This repository has been archived by the owner on Nov 1, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Tracing a bad deployment/HelmRelease #2028
Labels
Comments
|
Does that answer your question @usamaahmadkhan ? If not, what would you like to see (i.e., what should be the next step here)? |
Related: #1340 |
Flux v2, based on the GitOps Toolkit, has support for health assessment of deployments https://toolkit.fluxcd.io/components/kustomize/kustomization/#health-assessment |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I am deploying HelmRelease through flux. And many times Flux applies the manifest but HelmOperator fails due to bad configuration. How can I trace a bad deployment?
e.g. I updated a chart version from 1.0 to 1.1
Scenario 1:
chart 1.1 does not exist, Flux applies the manifest successfully but HelmOperator errors saying Chart does not exist.
Scenario 2:
chart 1.1 gets deployed but there was a configuration issue. Now chart 1.0 is removed but chart 1.1 also cannot be deployed due to config issue increasing down time.
Is there a way we can track/trace these two scenarios without having to look into logs manually And ensuring 100 percent uptime?
Can there be any alert/any other method for this so that I know exactly if a helm release fails and if I can either roll back or fix to avoid downtime
The text was updated successfully, but these errors were encountered: