-
Notifications
You must be signed in to change notification settings - Fork 634
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Network Policies don't have a selector on them #764
Comments
Why would deploy other things than Flux in flux-system namespace?
|
We didn't deploy other pods into flux-system but instead deployed flux into an already existing namespace. We understand that
Yes this makes sense if flux is deployed into a namespace it creates, but if it's deployed into an already existing namespace, it shouldn't delete that namespace since it didn't create it. |
Fixed in #891 |
Fixed in #891 |
As there are no plans to add pod selectors to the network policies at this moment and the other concerns have been addressed, I am closing this issue. If you still feel they should be added and/or that your request has not been fulfilled, feel free to re-open. ✨ |
Update link to v1beta2 in the API spec
The Network policies deployed as a part of
flux intstall
don't have any pod selectors defined on them, meaning if they are deployed into a namespace that has other pods running, it blocks all traffic to other pods in that namespace.flux2/manifests/policies/deny-ingress.yaml
Line 11 in 6add511
flux2/manifests/policies/deny-ingress.yaml
Line 14 in 6add511
Ideally, these policies should only be applied to the flux pods and not across everything in the namespace that flux has been deployed into.
We also discovered that when uninstalling flux v2, if you don't delete the namespace it doesn't remove these network policies.
The text was updated successfully, but these errors were encountered: