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

Adds support to explicitly configure network policy in injector #466

Closed
wants to merge 1 commit into from

Conversation

ryanmt
Copy link

@ryanmt ryanmt commented Mar 9, 2021

Similar to the conversion around PR #381, network policies are useful for the injector independent of openshift. This allows support for those use cases but similarly will require some configuration changes for openshift users.

Similar to the conversion around PR hashicorp#381, network policies are useful
for the injector independent of openshift.  This allows support for
  those use cases but similarly will require some configuration changes
  for openshift users.
@hashicorp-cla
Copy link

hashicorp-cla commented Mar 9, 2021

CLA assistant check
All committers have signed the CLA.

@@ -1,4 +1,4 @@
{{- if and (eq (.Values.injector.enabled | toString) "true" ) (and (eq (.Values.global.enabled | toString) "true") (eq (.Values.global.openshift | toString) "true") ) }}
{{- if eq (.Values.injector.networkPolicy.enabled | toString) "true" }}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe this would create a networkPolicy even if you disabled the injector, which shouldn't happen.

@jasonodonnell
Copy link
Contributor

Bumping this 😄

@ryanmt
Copy link
Author

ryanmt commented May 12, 2021

I ran into some issues I didn't end up chasing down yet. I'll close this since I don't have immediately plans to revisit.

@ryanmt ryanmt closed this May 12, 2021
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.

3 participants