How To Package And Distribute Crossplane Compositions As Container Images
ฝัง
- เผยแพร่เมื่อ 2 ต.ค. 2024
- Crossplane allows you to define your own composite resources (XRs) and compositions, then package them up to be easily distributed as OCI images.
▬▬▬▬▬▬ 🔗 Additional Info 🔗 ▬▬▬▬▬▬
➡ Gist with the commands: gist.github.co...
🎬 Crossplane Compositions: • How To Shift Left Infr...
How do I add a different providerconfig name for AWS other than the name default when deploying an EKS cluster resource?
Sorry for not responding earlier. I missed this message....
When you deploy a provider config, you give it a name. Later on, you can reference that config in any of the resources you define in a composition.
Great video. Thanks for efforts. I have a question on this, how to package controllerconfig required for provider? In my case, I want to pass debug arg to controller pod also, want 2 replicas and leader-election arg added, also need to pass service account name to be used. is there any way to package that as well? how could you address this? TIA
Great video. I have a question about claims and how we can "instruct" them to use a specific version of the package. Say for example we have package k8s and it is installed (for example version 0.0.1). And we apply a aws-eks.yaml claim, then we update the k8s package (change something in the composition, some parameters) and install it, so now we have version 0.0.2 (And this is the active version). How we can "update" our claim to use the new version 0.0.2?
The answer depends on the API versions used in Compositions. Byh default, if Composition versions stay the same, all resources using those compositions will be updated. On the other hand, if you do change the version, everything will stay the same until resources using those compositions update versions as well. It's the same model followed by Kubernetes itself.
Now, the important thing to note is that Composition versions are not the same as package versions.
@@Upbound Thanks a lot for the answer.
This is soooo cool!