-
Notifications
You must be signed in to change notification settings - Fork 201
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
Read aso-controller-settings ConfigMap via volume rather than env variables #4168
base: main
Are you sure you want to change the base?
Conversation
/ok-to-test sha=27873f2 |
I may hold off on merging this until we re-enable KIND tests as they're the primary test of this change. While I've tested it locally and it works it may be safer to wait to merge until those tests are re-enabled. |
/ok-to-test sha=27873f2 |
27873f2
to
7c36469
Compare
This has some possible disadvantages during upgrades that change the configmap, as there's just one ConfigMap which means the old pod may exit early (due to configmap change). Need to do some testing around that. |
Moving from a model where we have to explicitly set each secret in the pod env to a model where we just mount the whole secret into the pod. This has the added benefit of allowing us to autodetect secret changes and restart the pod AND means that users can totally omit the secret now as opposed to having to create the secret with empty values.
7c36469
to
6783a9f
Compare
Moving from a model where we have to explicitly set each secret in the pod env to a model where we just mount the whole secret into the pod. This has the added benefit of allowing us to autodetect secret changes and restart the pod AND means that users can totally omit the secret now as opposed to having to create the secret with empty values.
If applicable: