We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I set up default policy server with pull secret. When I remove pull secret later it has no effect on active policy server deployment.
Default configuration has no pull secret
~ helm get values -n kubewarden kubewarden-defaults USER-SUPPLIED VALUES: null ~ k get deploy -n kubewarden policy-server-default -o yaml | grep secret-registry
Set up pull secret and see changes as expected
~ kubectl --namespace kubewarden create secret docker-registry secret-registry-docker \ --docker-username=testuser \ --docker-password=testpassword \ --docker-server=192.168.64.2.nip.io:30707 ~ helm upgrade --wait --reuse-values --set policyServer.imagePullSecret=secret-registry-docker --namespace kubewarden kubewarden-defaults kubewarden/kubewarden-defaults ~ helm get values -n kubewarden kubewarden-defaults USER-SUPPLIED VALUES: policyServer: imagePullSecret: secret-registry-docker ~ k get deploy -n kubewarden policy-server-default -o yaml | grep secret-registry secretName: secret-registry-docker
Remove pull secret has not effect on running policy-server
~ helm upgrade --wait --reuse-values --set policyServer.imagePullSecret=null --namespace kubewarden kubewarden-defaults kubewarden/kubewarden-defaults ~ helm get values -n kubewarden kubewarden-defaults USER-SUPPLIED VALUES: policyServer: {} ~ k get deploy -n kubewarden policy-server-default -o yaml | grep secret-registry secretName: secret-registry-docker
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Current Behavior
I set up default policy server with pull secret. When I remove pull secret later it has no effect on active policy server deployment.
Steps To Reproduce
Default configuration has no pull secret
Set up pull secret and see changes as expected
Remove pull secret has not effect on running policy-server
The text was updated successfully, but these errors were encountered: