Feedback Loop for Claim and Composite/MRs

[ggkhrmv]

What problem are you facing?

As of now there is no way to know, if a new Claim Generation has been applied to a cluster, since there is no Feedback Loop from Composite/MRs to Claim.

Created (and later updated) Composite/MRs don't give a feedback on Claim Generation used to create and update those resources. This leads to intransparency on current state of resources on the cluster and impacts the ability to automate processes which involve Claims and MRs.

We use Crossplane Functions in our Setup. Since Composites and Claims are reconciled separately, we can't patch Claim Gen into the Composite.

How could Crossplane help solve your problem?

A "chain" should be implemented, to offer a feedback loop between claims and composites/MRs: XRC Generation -> XR Spec -> MR Spec -> MR Status -> XRC Status.

Using this approach would offer a higher transparency regarding the current state of composite, MRs and claim.

We could implement a new status field: .claimGeneration. This would allow the user to see the Generation of the Claim used to create and update the Composite as well the Condition of the composite.

[jbw976]

This sounds similar to the intent/ideas in the below issues:

• Enable user to understand when resource is reconciled #4655
• Enable user to understand when external resource is reconciled #4695
• Propagate claim generation to composite and managed resources #4659

We did make some progress on #4655 with crossplane/crossplane-runtime#633, but as @negz mentioned in #4655 (comment) and #6229 (comment), it isn't fully wired up yet. Looks like some progress is being made though in crossplane/crossplane-runtime#789. There could be some more progress on that in the context of #6229, so keep an eye on how that design shapes up. I don't think it would cover the full scope of this issue you're describing here, but it could be nice progress for the underlying machinery that would be needed 😇

[github-actions]

Crossplane does not currently have enough maintainers to address every issue and pull request. This issue has been automatically marked as stale because it has had no activity in the last 90 days. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh will mark this issue as not stale.

[github-actions]

Crossplane does not currently have enough maintainers to address every issue and pull request. This issue has been automatically marked as stale because it has had no activity in the last 90 days. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh will mark this issue as not stale.