❓*Here are some questions we didn’t get to answer yesterday:* Q1. What is your experience on debugging crossplane resources when desired state is not in sync and failing resources. In terraform your would see the conflict on CLI. How to monitor for failed resources for example? Q2. How does crossplane handle drift relating to persistent data stores in kubernetes? we cannot have databases being deleted Q3. How does one enforce a “golden path” yet have specific sandbox protocol for “off road” experimental deployments? Q4. I heard about EKS environment build on crossplane ? Is it true ?

see https://docs.crossplane.io/latest/cli/command-reference/#beta-trace

Q2: There's a

deletionPolicy

you can use in this case: https://docs.crossplane.io/latest/concepts/managed-resources/#deletionpolicy . With that you can prevent Crossplane from deleting your DBs

Q3: Building Compositions should be seen as building golden paths - that's their purpose. For sandboxing you'll need different environments I guess, maybe also a "sandbox management cluster" with another Crossplane instance for playing and experimenting. As I would recommend to fully automate the Crossplane setup anyways, this should be available in a few minutes. With that you could even implement "Crossplane sandbox on demand" 🙂

Q4: I don't really get the question: But there are definitely EKS Compositions around you can have a look on. I also build one myself, since I didn't found really good working solutions for me: https://github.com/jonashackt/crossplane-eks-cluster