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
k8s.io/kubernetes/cmd/kubeadm/app/util.ParseHostPort
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/app/util/endpoint.go:111
k8s.io/kubernetes/cmd/kubeadm/app/util/config.SetClusterDynamicDefaults
must be a valid IP address or a valid RFC-1123 DNS subdomain
as you can see the error comes from kubeadm when setting the controlPlaneEndpoint field in the ClusterConfiguration object.
this field must be an IP or a DNS name.
kubeadm uses a k8s utility function that misleadingly claims that it follows RFC-1123.
yet that RFC does allow underscores. this is more of a limitation for hostnames.
in any case, hostnames with underscores or capital letters should not reach the kubelet - i.e. the kind node containers ideally should not have _
What happened:
What you expected to happen:
Creation successful
How to reproduce it (as minimally and precisely as possible):
kind create cluster name_with_underscore
Anything else we need to know?:
This "phenomenom" was also spotted in the following issues afaik :
May be the regular expression
^[a-z0-9_.-]+$
L32 of kind/pkg/internal/apis/config/validate.go :kind/pkg/internal/apis/config/validate.go
Line 32 in 5e58a0d
^[a-z0-9.-]+$
(note that I don't know if this is used to validate something else... so maybe this correction isn't accurate).Environment:
The text was updated successfully, but these errors were encountered: