-
Notifications
You must be signed in to change notification settings - Fork 258
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
Use of ACK object status as healtchecks for FluxCD #1899
Comments
TIL about kstatus - thanks for sharing! We'll have to evaluate whether this is something we can implement in ACK or not. My quick thought is that most of ACK resources have a Status/Conditions, generally the
We currently have these resources: |
related #1345 |
Issues go stale after 180d of inactivity. |
/remove-lifecycle stale |
Issues go stale after 180d of inactivity. |
/remove-lifecycle stale |
Is your feature request related to a problem?
As an operator of cluster, I want to get the status of k8s objects aggregated in Kustomization status of FluxCD, so getting immediately the alert in slack if something goes wrong (embedded feature of fluxcd)
Describe the solution you'd like
The status of every object under ACK management must be in kstatus compatible format. So it would be always clear - is the object in reconciled state or no.
Also I am kindly asking to provide all necessary documentation for the end-user to be able to reproduce the proper manifests for every ACK managed object.
Describe alternatives you've considered
no options.
The text was updated successfully, but these errors were encountered: