Repository navigation
[virtual-machine] Revert per-vm network policies - #1611
Conversation
Signed-off-by: Andrei Kvapil <[email protected]>
WalkthroughNetwork policy restrictions and related annotations are removed from virtual machine and instance templates. The tenant template's endpoint selector is changed to select all endpoints instead of filtering based on external communication policy settings. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes
Suggested reviewers
Poem
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary of ChangesHello Andrei Kvapil (@kvaps), I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request reverts the implementation of per-virtual machine network policies. The changes involve removing specific Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on Gemini (@gemini-code-assist) comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request reverts the per-virtual-machine network policy feature. The changes correctly remove the per-VM CiliumNetworkPolicy resources and associated annotations from the virtual-machine and vm-instance charts, and simplify the tenant-wide allow-external-communication policy to apply to all pods. While the revert is logical, I've identified a potential high-severity issue. The removed per-VM policies allowed ingress from other pods in the cluster (fromEntities: - cluster). This rule appears to be missing from the tenant-wide policy that now governs the VMs, which could break previously working intra-cluster communication.
|
Successfully created backport PR for |
Signed-off-by: Andrei Kvapil <[email protected]> <!-- Thank you for making a contribution! Here are some tips for you: - Start the PR title with the [label] of Cozystack component: - For system components: [platform], [system], [linstor], [cilium], [kube-ovn], [dashboard], [cluster-api], etc. - For managed apps: [apps], [tenant], [kubernetes], [postgres], [virtual-machine] etc. - For development and maintenance: [tests], [ci], [docs], [maintenance]. - If it's a work in progress, consider creating this PR as a draft. - Don't hesistate to ask for opinion and review in the community chats, even if it's still a draft. - Add the label `backport` if it's a bugfix that needs to be backported to a previous version. --> ## What this PR does Revert per-vm network policies functionality introduced by #1611 As it is not working as expected any way. This is temporary solution before implementing full-fledged security groups in Cozystack fixes #1601 alternative solution: #1602 ### Release note <!-- Write a release note: - Explain what has changed internally and for users. - Start with the same [label] as in the PR title - Follow the guidelines at https://github.com/kubernetes/community/blob/master/contributors/guide/release-notes.md. --> ```release-note [virtual-machine] Revert per-vm network policies ```
Signed-off-by: Andrei Kvapil <[email protected]> <!-- Thank you for making a contribution! Here are some tips for you: - Start the PR title with the [label] of Cozystack component: - For system components: [platform], [system], [linstor], [cilium], [kube-ovn], [dashboard], [cluster-api], etc. - For managed apps: [apps], [tenant], [kubernetes], [postgres], [virtual-machine] etc. - For development and maintenance: [tests], [ci], [docs], [maintenance]. - If it's a work in progress, consider creating this PR as a draft. - Don't hesistate to ask for opinion and review in the community chats, even if it's still a draft. - Add the label `backport` if it's a bugfix that needs to be backported to a previous version. --> ## What this PR does Revert per-vm network policies functionality introduced by #1611 As it is not working as expected any way. This is temporary solution before implementing full-fledged security groups in Cozystack fixes #1601 alternative solution: #1602 ### Release note <!-- Write a release note: - Explain what has changed internally and for users. - Start with the same [label] as in the PR title - Follow the guidelines at https://github.com/kubernetes/community/blob/master/contributors/guide/release-notes.md. --> ```release-note [virtual-machine] Revert per-vm network policies ```
Signed-off-by: Andrei Kvapil [email protected]
What this PR does
Revert per-vm network policies functionality introduced by #1611
As it is not working as expected any way.
This is temporary solution before implementing full-fledged security groups in Cozystack
fixes #1601
alternative solution: #1602
Release note