Closed carreter closed 2 weeks ago
Log dump here!
Yes, this isn't supported, you're using a namespace reserved for Kubernetes and Kubelet will not allow you to do this if it's not an approved value.
You should use a different namespace for your custom labels / values.
https://kubernetes.io/docs/reference/labels-annotations-taints/
Kubernetes reserves all labels and annotations in the kubernetes.io and k8s.io namespaces.
/remove-kind bug /kind support /close
@BenTheElder: Closing this issue.
(also https://github.com/kubernetes-sigs/apiserver-network-proxy/pull/631#discussion_r1638814663, and if you check the kubelet log kubelet should have a message about this)
Got it, makes sense. Thanks for the fast response!
this is also #3536, we may attempt to validate these earlier
What happened: Creation of a cluster hangs or fails on the "Joining worker nodes" step if
node-role.kubernetes.io/worker: ""
is added as a label. It seemskubelet
is failing to start:What you expected to happen: Cluster should start and label nodes with appropriate role.
How to reproduce it (as minimally and precisely as possible):
kind create
with the following config:Anything else we need to know?: I believe it's something specifically about the
node-role.kubernetes.io
label that's breaking it.kind create
with another label succeeds:Environment:
kind version
): v0.23.0docker info
,podman info
ornerdctl info
): Server Version: 20.10.21/etc/os-release
): gLinux Rodete (Debian), kernel:6.6.15-2rodete2-amd64
kubectl version
): v1.30.0