From ccedc558b2f2839881c8a47c0e316f0b0b615418 Mon Sep 17 00:00:00 2001 From: Joseph Heck Date: Fri, 13 Oct 2017 15:30:11 -0700 Subject: [PATCH] adding explanation for product_uuid uniqueness (#5885) added steps for how to verify macaddress and product_uuid with reference to the bug in github that identified this need originally (https://github.com/kubernetes/kubeadm/issues/31) --- docs/setup/independent/install-kubeadm.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/docs/setup/independent/install-kubeadm.md b/docs/setup/independent/install-kubeadm.md index 00d279750f..cfd36326ff 100644 --- a/docs/setup/independent/install-kubeadm.md +++ b/docs/setup/independent/install-kubeadm.md @@ -24,6 +24,16 @@ please see [here](https://kubernetes.io/docs/concepts/cluster-administration/net {% capture steps %} +## Verify the MAC address and product_uuid are unique for every node + +* You can get the MAC address of the network interfaces using the command `ip link` or `ifconfig -a` +* The product_uuid can be checked by using the command `sudo cat /sys/class/dmi/id/product_uuid` + +It is very likely that hardware devices will have unique addresses, although some virtual machines may have +identical values. Kubernetes uses these values to uniquely identify the nodes in the cluster. +If these values are not unique to each node, the installation processes +[can fail](https://github.com/kubernetes/kubeadm/issues/31). + ## Check required ports ### Master node(s)