Docs and interoperability for using Crossplane with KRO (Kubernetes resource orchestrator) #940
Description
What problem are you facing?
Recently AWS started promoting the combination of ACK (AWS Controllers for Kubernetes) + KRO (Kubernetes Resource Operator), both in AWS summits and CNCF events.
ACK, supported by AWS, is a kubernetes controller for creating resources on it's platform, and KRO is a tool for grouping together resources using CRDs, being able to define dependencies between them, and allowing variables and outputs between them, and probably other capabilities.
Together, these can be used for building infrastructure on AWS using Gitops on a kubernetes cluster, figuratively speaking, a "non cloud-agnostic" crossplane.
AWS has also open-sourced kro, and made it agnostic to cloud provider. I've seen it interacts GCP's config-connector, which also aims to allow managing resources on GCP using kubernetes.
From my little knowledge of Crossplane It seems KRO is a too which is a "conceptual competitor" to crossplane features like compositions (and maybe other features), because it:
Allows the ability to create a custom resource out of multiple resources without creating custom resource definition, and offers similar features to crossplane including being able to create dependencies between resources, passing variables from resource to resource, and other features which I probably don't know about.
How could Crossplane help solve your problem?
Since I assume Crossplane aims to be a superset of ACK (agnostic, multi-cloud), I suggest users should be able to use KRO with Crossplane, to have documentation for it's usage and interoperability.
Since all I ever did on Crossplane was creating VPC+buckets+VMs on GKE using ArgoCD on K3s, I might be missing out on many things, so please correct me if I'm missing things.