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
The OpenStack cloud provider currently uses the name of the kubelet node to register with the API server. However the name is not guaranteed to conform to the DNS-1123 subdomain spec.
Given a node name of worker/925f11f3-80af-4844-a00e-f0af521779d1, the following message appears in the kubelet logs:
Unable to register node "worker/925f11f3-80af-4844-a00e-f0af521779d1" with API server: Node "worker/925f11f3-80af-4844-a00e-f0af521779d1" is invalid: metadata.name: Invalid value: "worker/925f11f3-80af-4844-a00e-f0af521779d1": a DNS-1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is 'a-z0-9?(.a-z0-9?)*')
What you expected to happen:
The OpenStack Cloud provider uses the instance id instead of the instance name. This will guarantee that the id conforms the DNS-1123 spec without making any assumptions on what the instance name may be.
How to reproduce it (as minimally and precisely as possible):
In the OpenStack console, rename a kubelet node to kubelet/1234 and attempt to register the kubelet node to the api server.
Cloud provider or hardware configuration: OpenStack
OS (e.g. from /etc/os-release): Ubuntu 14.04.5
Kernel (e.g. uname -a): Linux b4fdd4bc-cab9-44ff-9c99-44e91ff5b414 4.4.0-103-generic Suggest people verify they can start a VM on GCE. #126~14.04.1-Ubuntu SMP Mon Dec 4 19:33:04 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
What happened:
The OpenStack cloud provider currently uses the name of the kubelet node to register with the API server. However the name is not guaranteed to conform to the DNS-1123 subdomain spec.
Given a node name of
worker/925f11f3-80af-4844-a00e-f0af521779d1, the following message appears in the kubelet logs:What you expected to happen:
The OpenStack Cloud provider uses the instance id instead of the instance name. This will guarantee that the id conforms the DNS-1123 spec without making any assumptions on what the instance name may be.
How to reproduce it (as minimally and precisely as possible):
In the OpenStack console, rename a kubelet node to
kubelet/1234and attempt to register the kubelet node to the api server.Anything else we need to know?:
Environment: OpenStack Newton
kubectl version):uname -a): Linux b4fdd4bc-cab9-44ff-9c99-44e91ff5b414 4.4.0-103-generic Suggest people verify they can start a VM on GCE. #126~14.04.1-Ubuntu SMP Mon Dec 4 19:33:04 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux