You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: