flagger
flagger copied to clipboard
Alternative ways to promote canary without skipAnalysis: true
Currently, the only way to skip analysis and promote a canary directly is by adding skipAnalysis: true to the Canary spec. This approach has limitations:
- Requires spec modification and redeployment - Not suitable for emergency situations
- Not runtime controllable - Can't make promotion decisions dynamically
- Impractical for large deployments - Need to modify many Canary resources
- No rollback capability - Once set, requires another spec change to re-enable analysis
-
ArgoCD reverts manual patches -
kubectl patchcommands get overwritten on sync
Is there any other way to promote canaries to 100% traffic without modifying Canary specs?