Skip to content

Commit

Permalink
adding explanation for product_uuid uniqueness
Browse files Browse the repository at this point in the history
added steps for how to verify macaddress and product_uuid with
reference to the bug in github that identified this need originally
(kubernetes/kubeadm#31)
  • Loading branch information
heckj committed Oct 12, 2017
1 parent 04fc9a3 commit d768c91
Showing 1 changed file with 10 additions and 0 deletions.
10 changes: 10 additions & 0 deletions docs/setup/independent/install-kubeadm.md
Expand Up @@ -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)
Expand Down

0 comments on commit d768c91

Please sign in to comment.