From b4ff1b21a46a74e930f36cec67028b15135d49fd Mon Sep 17 00:00:00 2001 From: Marcus Noble Date: Tue, 20 Apr 2021 14:16:00 +0000 Subject: [PATCH] Add 'content/posts/kubernetes-label-length.md' --- content/posts/kubernetes-label-length.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 content/posts/kubernetes-label-length.md diff --git a/content/posts/kubernetes-label-length.md b/content/posts/kubernetes-label-length.md new file mode 100644 index 0000000..22ef955 --- /dev/null +++ b/content/posts/kubernetes-label-length.md @@ -0,0 +1,15 @@ +--- +title: "Kubernetes label length" +date: 2021-04-20T15:10:37+01:00 +draft: false +tags: + - kubernetes +images: +- /images/kubernetes-label-length.gif +--- + +It turns out that labels _values_ in Kubernetes have a limit of 63 characters! + +I discovered this today when none of my nodes seemed to be connecting to the control plane. Eventually discovered the hostname of the node was longer than 63 characters (mainly due to multiple subdomain levels) and so the `kubernetes.io/hostname` label being automtically added to the node was causing Kubernetes to reject it. + +If you hit this like me, the hostname used for the label can be [overridden using the `--hostname-override` flag on kubelet](https://kubernetes.io/docs/reference/labels-annotations-taints/#kubernetesiohostname) or by setting the value of the label yourself with the `--node-labels` flag. \ No newline at end of file