KRO Status Conditions

[n3wscott]

Feature Description

Problem Statement:

The conditions defined in the schema of a CRD from an RGD should align with the “single top-level condition” pattern. By not needing to know the implementation details of the controller reconciling the resource and only looking at the “top-level” condition, we enable a form of duck-typing on readiness that allows the ecosystem to create safer interactions.

We will adhere to the advice from upstream Kubernetes API Conventions, except we will strongly prefer normal-true (positive polarity) conditions.

Since a Resource Graph will continue to update the downstream resources based on the RGD template, it will always have a Ready condition as its top-level condition. Based on the implementation of the controller in KRO, we will have sub-conditions that describe the major work of the Resource Graph reconciler.

Proposed Solution:
KRO Status Conditions

Alternatives Considered:
None.

Additional Context:
See document.

• Please vote on this issue by adding a 👍 reaction to the original issue
• If you are interested in working on this feature, please leave a comment

[n3wscott]

I am happy to do this work, or help someone do the work with me.

[fsommar]

Hey, I created a similar issue too #415

[n3wscott]

I landed the RGD conditions but I would like to do a pass on Instance conditions. It could be for 0.5.

[n3wscott]

I think #602 is a dup of this.

[github-actions]

This issue has been marked stale due to 30 days of inactivity. Maintainers use this label for hygiene. Comment or add a relevant label (keepalive) to keep it from becoming stale.