-
Notifications
You must be signed in to change notification settings - Fork 0
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
Kubernetes Change Tracking: Add reloader to roll deployments after env or secret changes #6
Comments
clone/fork reloader
follow
test tracking of env vairables via reloader https://github.com/stakater/Reloader/blob/master/README.md#how-to-use-reloader
|
Simulating change to force a deployment redeploy
|
deleted/recreated deployment/service
|
Try certificate modification - dns
|
attempt to verify that the reloader is picking up the www to www2 dns change
try one more time - turn off reloader on deployment, attempt multiple changes on the certificate dns name |
retrying delete of certificate
secret in the pod is unchanged
michaelobrien@mbp8 eks % kubectl describe certificate www unchanged STAKATER_WWW_TLS_SECRET: c94f58ebc4942ee95afb3b1cfb2d8dbdec17fcf1
|
the uid changes on secret deletion
|
On M1 Max - verify helm charts as opposed to kubernetes raw yamls
add cert-manager - follow #3
|
reloader kicks in a 2nd time on a secret delete after a certificate change (dns) helm install stakater/reloader --generate-name --set reloader.reloadOnDelete=true
use case: change dns on cert - apply, then delete old secret from previous - triggers reloader example
|
Options for deployment rollout on config change
tracking
ObrienlabsDev/blog#81
The text was updated successfully, but these errors were encountered: