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

imageCredentials.name value for Kube-Enforcer Chart discrepancy #771

Open
JakeMeloche opened this issue Sep 11, 2023 · 2 comments
Open

imageCredentials.name value for Kube-Enforcer Chart discrepancy #771

JakeMeloche opened this issue Sep 11, 2023 · 2 comments

Comments

@JakeMeloche
Copy link

the imageCredentials.name value should be aqua-registry-secret not aqua-registry.

https://github.com/aquasecurity/aqua-helm/blob/2022.4/kube-enforcer/values.yaml#L35C4-L35C26

@semyonmor
Copy link
Collaborator

@JakeMeloche why?

@spimmer
Copy link
Contributor

spimmer commented Feb 9, 2024

@semyonmor Because Documentation instructs to create the pull secret with name aqua-registry-secret:

kubectl create secret docker-registry aqua-registry-secret --docker-server="registry.aquasec.com" --namespace aqua --docker-username="[email protected]" --docker-password="<Password>" --docker-email="[email protected]"

Furthermore the default value is aqua-registry-secret in the helpers file:

{{ .Values.global.imageCredentials.name | default (printf "aqua-registry-secret") }}

So to me it makes sense to use this de facto standard name in the values.yamltoo:

name: "aqua-registry"

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

No branches or pull requests

3 participants