This article explains how to manage the infrastructure of your clusters in the Cloud Panel.
When you create a cluster, the master and its workers are displayed in both the Infrastructure > Server area and the Container Cluster > Cluster section is displayed. The master and workers of the cluster can be uniquely identified using the naming convention. Examples: onekbje4k5-master-1, onekbje4k5-worker-1, onekbje4k5-worker-2
In the Infrastructure > Server area, you can restart and deactivate the master and workers of your cluster. You can also assign an additional IPv4 and/or IPv6 address to the master and associated workers and assign an existing firewall policy in this area.
Administration of the cluster
In the section Container Cluster >Cluster you can add or delete nodes to your cluster. You also have the option to configure your autoscaler so that the size of your cluster is automatically adjusted to the requirements of the workload to be executed, if necessary. In this area, you can also add additional development solutions to your cluster to extend it.
Please note: Using these options may cause clusters to stop working properly. Use these options with extreme caution.
Management of Persistent Storage(s)
You can find an overview of the created block or persistent storages that you use with your cluster or clusters in the Infrastructure > Block Storage area. However, you can only manage your Persistent Storages to a limited extent in this area. In this context, please note the following information regarding the creation and deletion of persistent storages.
Creation of Persistent Storages
You have the following options for creating a persistent storage:
You install a solution, such as Kubeless, that requires block or persistent storage. The installation of a solution is possible either during the creation of a cluster or with already existing clusters in the area Container Cluster > Cluster > Solutions. During the installation of the solution, a Persistent Storage is automatically created. Furthermore, Kubernetes is configured so that the persistent storage can be used immediately in the cluster.
- You use the Kubernetes tools (for example, kubectl, the Kubernetes API, or the Kubernetes Dashboard) to run a Kubernetes manifest that contains a Persistent Volume Claim. In the Persistent Volume Claim, you specify the size of the Persistent Storage.
Deletion of Persistent Storages
Please note: If you delete a Block or Persistent Storage in the Infrastructure > Block Storage area, the Persistent Storage is not automatically released in Cubernet. Therefore, make sure that your Persistent Storages are always removed in Kubernetes by deleting the Persistent Volume Claims. This is the only way to ensure that Kubernetes releases persistent storage in the cluster.
Firewall policy management
In the Network > Firewall Policies pane, you can create, edit, duplicate, and assign firewall policies to the nodes in your cluster.
Management of private networks
For each cluster, a private network is automatically created and assigned the masters and workers contained in the cluster. You can manage these private networks in the Network > Private Network area.
Please note: If you change the private network settings, the functionality of the cluster may be affected. For example, if you unassign the master to the private network, the cluster will no longer work.