Crossplane: Support configurable names for provisioned resources (e.g., cluster)
Related: #624
What problem are you facing?
When a cluster is provisioned through crossplane, it generates a random name like, gke-0eb7ce43-xxxx-xxxx-xxxx-xxxxxxxxxxxx for the cluster. This makes it difficult to distinguish between clusters.
How could Crossplane help solve your problem?
Adding labels help but being able to control the name of the cluster being provisioned would be great. We can have something like custom-prefix-xxxx-xxxx(some uuid with it) or even allow providing static names for the cluster and throw an error if the cluster with the same name already exists.
I saw some docs referring to external-name here and PR related to it. It seems to implement external-name in annotations. I tried setting this in my kubernetescluster resource but it doesn't seem to work.
vadasambar
All 3 comments
External name annotation isn't used by k8s cluster resources yet. Hopefully, all resources will use it in the 0.6 release.
muvaf
on 15 Nov 2019
External name annotation works in 0.6 release. :smile:
Closing this issue.
vadasambar
on 30 Dec 2019
Thank you for following up and confirming @vadasambar! 馃
jbw976
on 1 Jan 2020
Related issues
hasheddan
路
6Comments
hasheddan
路
5Comments
jbw976
路
6Comments
negz
路
3Comments
timstoop
路
4Comments
Most helpful comment
External name annotation isn't used by k8s cluster resources yet. Hopefully, all resources will use it in the 0.6 release.