The best features Upbound Crossplane offers include that we have templating all the resources, which is called XCRDs and these are easy to manage. When the resource is created in the Kubernetes cluster itself, it is quite easy to manage through that, and we don't have to track everything on the cloud platform. Everything is in our Git repo which is there as infrastructure as code, wherein our Helm templating is there and Go templating is there, which helps us to create automation for Upbound Crossplane. We have separate clusters for Upbound Crossplane. XCRDs and templating have made my workflow easier and more efficient because Upbound Crossplane is a great product to replace Terraform. In our case, we had a lot of drift scenarios with Terraform and it was difficult to manage because in our organization we also have our own native solutions. Those providers are something that helps us automate and set up end-to-end automation for provisioning, whether it is any kind of resource, whether it is a secret or secret replications across different cloud providers.
