Today there is a new opensource tool for kubernetes, is the case of KRO (Kube Resources Orchestator). This a experimental project created by AWS, by the moment in phase beta and not is recommend for productions environment.
When validating this project I see that it is another tool like Crossplane with a big difference in maturity, both can do the same, but competition is always good, so welcome.
Comparating crossplane and KRO
In crossplane for you create an API you need to create a CompositeResourceDefinition and a Composition with this you are enabled your developers for create an claim and deploy applications as API, but in KRO is a little different, the concept is similar but you need an ResourceGroup where are defined all components of the API for that the developers can be create the Application as Instances.
How to Work KRO.
Check the offical documentacion
Check my blog related to ACK Controller.
Creating Infraestructure with the ACK from EKS AWS
Kro is simple and easy, Kro uses a single ResourceGroup to define and manage collections of Kubernetes resources and automatically creates CRDs and controllers for your custom resources.
How to Work Crossplane.
Check my lasts blogs.
Crossplane + AWS Overview for Managing Infrastructure as Code (IaC) with Kubernetes.
Crossplane AWS First Demo for Managing Infrastructure as Code (IaC) with Kubernetes..
Self-Service: Building and Enabling APIs with Crossplane and AWS
KCL + Crossplane: A Declarative Language for Deploying Complex Infrastructure on AWS with Kubernetes.
Compositions and Composite Resource Definitions are key configurations for composing higher-level APIs. The composite resource defines the schema of the new custom API, it is a definition of a new CRD and the Composition is the bridge between the new CRD schema and the existing managed resources.
Conclusion
KRO (Kube Resources Orchestator) is a new open-source tool for Kubernetes and this is an experimental project created by AWS and is currently in beta, I think that KRO is similar to Crossplane but less mature.Both help simplify complex applications or architectures for product teams or developers, allowing the complexity to be left to the platform teams.
Top comments (0)