Kro Explained | Kubernetes Resource Orchestrator | Simplify K8s APIs

[@mfreeman451]

looks amazing, will be trying this out shortly.

[@TechEagerVLogs]

Bro I had seen you in one of IBM's cloud video 😅😅

[@geowalrus]

How is it different from crossplane?

[@nR-kv7xo]

probably cloudformation under the hood Lol

[@svennam92]

Dives into this at 4:38. A critical difference is that kro works with all K8s resources (CRDs), not just specific providers. It's not limited to predefined or provider-specific resource abstractions.

[@RedbackThomson]

@@svennam92 So it handles the same things that the Crossplane provider-kubernetes does, except without requiring it to be wrapped in an Object?

[@svennam92]

@@RedbackThomson kro takes a simple approach. If it's a k8s resource, kro can work with it. This means essentially any controller is supported, including ACK.

[@joebowbeer]

Is it compatible with GitOps? An ArgoCD Application can contain a ResourceGroup, right? In which case, kro could provide the topo ordering that ArgoCD lacks.

[@Luther_Luffeigh]

I wish AWS uses engineers time and effort to invest in existing open source solutions like crossplane which already do this well