Magnum/CAPI provisioned Kubernetes cluster name length

[vexxhost]

Magnum/CAPI provisioned Kubernetes cluster name length

[mnaser]

@runlevel-six: I think this is an interesting problem, right now, we are generating cluster names in the following way:

https://github.com/vexxhost/magnum-cluster-api/blob/main/magnum_cluster_api/utils.py#L45-L58

We're using cluster name + 10 characters. Since we're creating all of them inside the magnum-system namespace, we can't really have clusters with the name only, unless we start creating clusters in different namespaces but that starts to get a little bit more complicated and becomes a much bigger change.

I think what we can do is probably drop that down to 5 characters, that might help a little bit?

[runlevel-six]

@mnaser I think that will definitely help, and we can work to shorten our cluster names as well. Any chance we can also shorten the node names since that is part of the overall length for some application applied labels?

I ask because in the example above, it looks like the name is foo-test-4admbibsdj-default-worker-infra-rb4bh-f2h5t which looks to be a mix of cluster name + 10 characters + worker name + 2 five character strings. In that example the cluster name was solely foo-test and all the rest is appended by Magnum.

[mnaser]

Unfortunately the server name component actually comes from the Cluster API so we have to look for something there

[runlevel-six]

Ok, thanks