[ASCN-227] Add support for Reloader in Kubernetes #13
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
stephen-vakil
approved these changes
Oct 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is for ASCN-227 and does the exact same thing as this Scheduler PR.
This PR follows these instructions to add the annotation to enable Reloader to the deployment. Reloader is already installed in the Kubernetes cluster by SRE. By having this annotation, Kubernetes will make sure pods are restarted when a secret or config map changes.
How to test
ascn-devthrough local CNABascn-devcluster in Lens and go to theOpServernamespace. There should be 1 pod that has been running for a while31s(so you don't have to wait 5 minutes after changing the GCP secret)my_okta_secret