Skip to content
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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

amir-badar
Copy link

@amir-badar amir-badar requested a review from a team July 14, 2023 19:36
@hashicorp-cla
Copy link

hashicorp-cla commented Jul 14, 2023

CLA assistant check
All committers have signed the CLA.

@amir-badar amir-badar changed the title Allows the release namespace to be overridden (#909) Making Injector NetworkPolicy Namespace Scoped (#909) Jul 14, 2023
@heatherezell
Copy link

Hello @amir-badar - thank you for this submission! Can you let me know, was this a miss from the linked PR? Thanks!

@amir-badar
Copy link
Author

@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.

@dlydiard
Copy link

dlydiard commented Jul 14, 2023

To give more context we are installing this chart with kustomize (helm enabled) + argo, so the namespace is required on the NetworkPolicy CR. The other injector charts seem to include the namespace, but it was missing for NetworkPolicy

@amir-badar
Copy link
Author

@hsimon-hashicorp Do you have an ETA as to when this will be approved?

Copy link
Contributor

@tomhjp tomhjp left a 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

templates/injector-network-policy.yaml Outdated Show resolved Hide resolved
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants