Instance no longer created using the "-control-plane-" convention.

[hlesesne]

This may have been intentional, but I didn't find it any the release notes. It appears that previous versions used the convention:

kube-string-string-control-plane-string for control planes and kube-string-string-default-worker-string for worker nodes.

Now it appears that control planes have dropped the -control-plane- convention, so instance names are kube-string-string-string. Worker nodes continue to use the -default-worker- convention.

This isn't a big deal at all, but I discovered it in a small test script that steps up a ssl proxy to the control plane and it looked for -control-plane- in the name. It's an easy fix in my script, but I wanted to mention it, just in case it was a regression and not intended.

[hlesesne]

getting_started.md does seem to still reference the convention:

magnum-cluster-api/docs/user/getting-started.md

Line 273 in 4f922d0

kube-7kjbp-control-plane-vxtrz-nhjr2 Ready control-plane,master 3d v1.25.3

[mnaser]

Hmm.. it seem that this change at some point probably with CAPI, let me see..

[mnaser]

I think this change happened when CAPI introduced kubernetes-sigs/cluster-api#9340 and not within the scope of the Cluster API but I'll dig in more.

[mnaser]

I believe this has nothing to do with the Cluster API, I think this is to do with a Cluster API update that you might have done at your side with the latest update that may have done that change.