Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Anchor
page1
page1

































DIGIT Documentation "Public Version"
Anchor
page2
page2
Infra Requirements

Requirements


Master Cluster

Six or more machines running one of:
Image Added
Ubuntu 16.04+
Image Added
Debian 9
Image Added
CentOS 7
Image Added
RHEL 7
Image Added
Container Linux (tested with 1576.4.0)
Image Added
4 GB or more of RAM per machine (any less will leave little room for your apps)
Image Added
2 CPUs or more
Image Added

User Cluster

One or more machines running one of:
Image Added
Ubuntu 16.04+
Image Added
Debian 9
Image Added
CentOS 7
Image Added
RHEL 7
Image Added
Container Linux (tested with 1576.4.0)
Image Added
2 GB or more of RAM per machine (any less will leave little room for your apps)
Image Added
2 CPUs or more
Image Added
Full network connectivity between all machines in the cluster (public or private network is fine)
Image Added
Unique hostname, MAC address, and product_uuid for every node. See here for more details.
Image Added
Certain ports are open on your machines. See below for more details.
Image Added
Swap disabled. You MUST disable swap in order for the kubelet to work properly.
Image Added


Verify the MAC Address and product_uuid Are Unique for Every Node
Anchor
page3
page3
Image Added You can get the MAC address of the network interfaces using the command ip link or ifconfig -a
Image AddedImage Added
The product_uuid can be checked by using the command sudo cat /sys/class/dmi/id/product_uuid
Image AddedImage Added
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 process may fail.

Check Network Adapters

If you have more than one network adapter, and your Kubernetes components are not reachable on the default route, we recommend you add IP route(s) so Kubernetes cluster addresses go via the appropriate adapter.

Check Required Ports

Master Cluster Master Node(s)
Image Added

Protocol

Direction

Port Range

Purpose

 

 

 

 

TCP

Inbound

6443*

Kubernetes API server

 

 

 

 

TCP

Inbound

2379-2380

etcd server client API

 

 

 

 

TCP

Inbound

10250

kubelet API

 

 

 

 

TCP

Inbound

10251

kube-scheduler

 

 

 

 

TCP

Inbound

10252

kube-controller-manager

 

 

 

 

TCP

Inbound

10255

Read-only kubelet API

 

 

 

 



Worker Node(s)& User Cluster Worker Nodes
Image Added

Protocol Direction Port Range Purpose
Image Added

Anchor
page4
page4
TCP

Inbound

10250

kubelet API

 

 

 

 

TCP

Inbound

10255

Read-only kubelet API

 

 

 

 

TCP

Inbound

30000-32767

NodePort Services**

 

 

 

 

Image Added

** Default port range for NodePort Services.

Any port numbers marked with * are overridable, so you will need to ensure any custom ports you provide are also open.