Kubernetes

Universal Compute Platform is built on Kubernetes middleware. Kubernetes provides a unifying structure for application delivery and provides integrated management of application state along with clustering capabilities.

Kubernetes components must be downloaded and installed during the cluster configuration stage. After you select the cluster type and initialize the cluster (a Standalone cluster for Self-Orchestration deployments), the appliance connects to Docker Hub to download and install the additional Kubernetes components based on your installation requirements.
Note

Note

Internet access is required during installation so that the required components can be downloaded. For details, see Firewall Requirements.

After the Standalone cluster is created, Kubernetes binds to the ICC IP address (either the physical ICC IP address or VRRP IP, if it's configured). Due this binding, an ICC IP address is required for all Self-Orchestrated deployments, although ICC connectivity is not required.

Note

Note

  • Because of the ICC binding, it's recommended to use the data ports for application management rather than the ICC ports.

  • Do not change the ICC addressing scheme, the hostname, or the domain name, once they are assigned. If you change the ICC IP address or ICC VRRP address, the Kubernetes binding breaks, and the Kubernetes installation unwinds, effectively wiping out the installation. In this case, the only fix is to reinstall and reconfigure. The user interface prevents modification of these parameters to preserve the integrity of the system. If adjustments are required, the node must be reset.

  • Kubernetes requires the reservation of two /16 subnets for use by the Pod and Service Networks (the default ranges are 10.96.0.0 and 10.97.0.0). Make sure that the ranges that you use do not overlap with routing domains.

Click to expand in new window
Kubernetes Middleware Layer