You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Another example:
It is highly irritating when you want to Check Compositions and the side starts with XRs (https://docs.crossplane.io/v1.10/concepts/composition/)
Please make it clear i.e.:
As an Infra I create Compostions and XRDs and the Consumer creates the Claim/XR.
Maybe using Kubernetes analogies would be fine aka:
While we still have our opinionated way [link2diff2NormaloCRDs] to use CRDs there is basically nothing new.
Think about Compositions as a declarative way to configure/create specific Controllers and XRDs are just opinionated CustomResourceDefinitions. So they create the CRD for the Consumer to use. We call it XR/Claim because ??? (placeholder for explanation Claim "vs" XR). In the end a "ConsumerController" picks (ok that would be the K8s-way in Crossplane it is the other way around) the Claim/Object and creates/configures(/watches?) it.
An approach like this would use patterns we know already and Compositions wouldn't be a Miracle Resource anymore (scnr).
Some feedback from a handsome community member in German thread in Linkedin:
What could be improved in the docs:
Overview of the Crossplane CRDs and how they are opinionated.
What is CompositionRef, ToCompositeFieldPath, FromCompositeFieldPath. Overview. Explanation
Relation of Claims, XRD, Compositions + XRs. Is documented. Still not clear.
What happens if there is no defaultCompositionRef and there are multiple Compositions.
For every opinionated Crossplane extension, there should be a section with explanation and diagram.
How to Monitoring
via @erkules
The text was updated successfully, but these errors were encountered: