aws-controllers-k8s
Use of ACK object status as healtchecks for FluxCD
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.
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 Status.Status field shows the value returned by the AWS APIs, which is not compatible with the statuses mentioned here.
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.
We currently have these resources:
- https://aws-controllers-k8s.github.io/community/reference/
- https://github.com/aws-controllers-k8s/examples/tree/main/resources
Issues go stale after 180d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 60d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/aws-controllers-k8s/community.
/lifecycle stale
Issues go stale after 180d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 60d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/aws-controllers-k8s/community.
/lifecycle stale
Issues go stale after 180d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 60d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/aws-controllers-k8s/community.
/lifecycle stale
Issues go stale after 180d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 60d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/aws-controllers-k8s/community.
/lifecycle stale