As of Platform version 8.2.0, you can add, manage, or remove a Kubernetes cluster through the Infrastructure>Clusters page in the SOC. In previous Platform versions, clusters are managed through the Infrastructure>Clouds page of the SOC.
As of Platform version 8.2.0, you can add mutli-clusters to a cloud on your Platform. In previous Platform versions, you could only add a single cluster to a cloud on your Platform, read more.
From the Infrastructure>Clusters page in the SOC, you can view all the clusters that have been added to your Platform.
For each Cluster the following information is displayed:
To attach a cluster, use the “Attach Cluster” button on the Clusters page of the SOC.
In the “Attach a Kubernetes cluster” window,
select a Cloud to attach the cluster. This will determine the URLs of the applications that are deployed to this cluster.
fill in the Cluster Name. This is used to identify the cluster on the Platform
fill in a Cluster Namespace the Platform should deploy applications to on the clusters. The Platform will automatically create this Namespace on the cluster when it is added to the Platform
fill in the full URL for the cluster. Include
https:// and the port to the Kubernetes API server (default 6443)
choose a Display Color. The color you choose is used to help visually group servers in this cluster on the Servers page
provide a comma separated list of host names or IP addresses of cluster nodes to use as Gateway Nodes. The Platform will route traffic through these nodes to the rest of the nodes on the cluster and must be able to reach nodes provided in this window. We recommend that you add at least 2 gateway nodes to handle traffic and to ensure high availability. See more about how gateway nodes are used by the Platform
After adding a Kubernetes Cluster to a Cloud, you are able to edit information about a cluster it by clicking the Edit button next to the corresponding cluster name in the Infrastructure> Clusters page.
This will open the Kubernetes cluster editor window where you can update the following cluster information: Cluster Name, URL, Authentication Mode and corresponding inputs, nodes to use as Gateway Nodes, and the Heapster URL.
You are not able to change the Cloud the cluster is attached to or the Namespace for the cluster.
Click Save when all changes have been made (or Cancel to not edit any information). After saving, the Platform will begin to run some validation on your cluster to make sure it meets the minimum requirements.
When validation is complete, you will be redirect to a page that displays how your cluster performed. Note that the Platform will update the cluster with the new information even if validation doesn’t succeed, however the cluster must pass validation before the Platform can properly manage or deploy workloads to it. If you have trouble passing validation, make sure all inputs are correct and re-run validation.
All clusters must be validated by the Platform to make sure the provided cluster information is correct and the Platform can access the parts of the cluster its needs to manage deployments. Cluster validation is run by default when a cluster is attached to the Platform or edited on Platform, but its recommended to manually run validation if the cluster is changed.
To run Platform validation on your cluster, click on the down arrow icon next to Edit for the cluster you want to validate and then click Validate.
When validation is complete, you will be redirected to a report on how your cluster performed.
As of Apprenda 8.2.0, you can apply Custom Properties to Kubernetes clusters. In previous Platform versions, Custom Properties could only be applied to Pods. By adding Custom Properties to clusters, you can use Application Deployment Policies to manage scheduling Kubernetes components that are deployed on the Platform.
To view Custom Properties assigned to a cluster, click on the down arrow icon next to Edit for the cluster you want to view the properties for and click View Custom Properties.
You can remove a Kubernetes cluster from your Platform through the Clusters page by clicking on the Remove action on the cluster’s drop-down menu.
Kubernetes components that are deployed on the cluster will not be undeployed before the cluster is removed from the Platform. If you are planning to reuse the cluster, you must manually undeploy or move workloads in the Platform, or delete the namespace after the cluster is removed from the Platform.
Once a cluster is removed, the Platform will mark any instance that was running on that cluster as undeployed. This may trigger new deployments on Platform if there are minimum instance counts set for your Kubernetes components.