-
Notifications
You must be signed in to change notification settings - Fork 59
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
Bug: cannot specify podsecuritypolicies #97
Comments
weitzj
pushed a commit
to devk-insurance/ambassador-chart
that referenced
this issue
Jul 1, 2020
If one want to use a custom `values.yaml` for their Helm chart, the bundled `values.yaml` of the existing Helm chart will get merged with the custom values.yaml. Since the bundled `values.yaml` defines an array `[]` for podsecuritypolicies, but the podsecuritypolicies.yaml template expects a map for `annotation:` and `spec:`, it is not possible to generate a valid Helm chart. The only workaround would be to ignore/delete the bundled values.yaml altogether. This PR fixes this issue by using a map: `{}` as a default value for the bundled `values.yaml` Fixes: - datawire#97
@nbkrause |
inercia
added a commit
that referenced
this issue
Jul 6, 2020
…-type Fix #97: Cannot specify podSecurityPolicies
❤️ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It is not possible to override the podsecuritypolicies, as they are defined as an "array", but referenced as a map
The text was updated successfully, but these errors were encountered: