-
Notifications
You must be signed in to change notification settings - Fork 880
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
Making Injector NetworkPolicy Namespace Scoped (#909) #922
base: main
Are you sure you want to change the base?
Making Injector NetworkPolicy Namespace Scoped (#909) #922
Conversation
Hello @amir-badar - thank you for this submission! Can you let me know, was this a miss from the linked PR? Thanks! |
@hsimon-hashicorp Is there a PR already raised for this issue? I can't see if you have put a reference link for that PR. The problem which I have found is when you deploy this helm chart in a custom namespace it throws an error about Network Policy being missing for Namespace and as I have dig down i found that this object is not namespace scoped and so it throwing InvalidSpecError. |
To give more context we are installing this chart with kustomize (helm enabled) + argo, so the namespace is required on the |
@hsimon-hashicorp Do you have an ETA as to when this will be approved? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for raising this, in addition to my suggested edit, please can we get a bats unit test for this to validate? It doesn't look like we have any unit tests for the network policy yet, so you'll need to add a new file in test/unit
Co-authored-by: Tom Proctor <[email protected]>
#909