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.

Sign up for GitHub

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

Jump to bottom

Track secrets and config maps #36

Closed

4 tasks done

stefanprodan opened this issue Jan 25, 2019 · 0 comments

Assignees

Labels

Member

stefanprodan commented Jan 25, 2019 •

edited

Flagger should track changes for secrets and config maps used by the target deployment.

Track changes tasks

discover secrets and config maps referenced by the target deployment
detect changes in secrets and config maps referenced by the target deployment
the primary bootstrap and promotion procedure should clone the target configs
trigger the canary analysis when a secret or configmap changes

stefanprodan added the kind/feature label

stefanprodan self-assigned this

stefanprodan mentioned this issue

Track changes in ConfigMaps and Secrets #37

Merged

stefanprodan closed this as completed in #37

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment