Manage Kubernetes Cluster

Overview

On this page, you can get a comprehensive view of your cluster, including key details and statistics, and access a list of all nodes within the cluster, providing insights into the cluster's composition.

Information on the page

Adding a domain and configuring traffic for the cluster

To ensure that your users can access the application running in your Kubernetes cluster, you need to specify and validate the domain and configure the correct redirection.

You can add a new domain when creating a cluster and configure it later on the cluster page, or you can create and configure it directly on the cluster page.

Adding a domain to an existing cluster

1. If you have an already created cluster, navigate to the cluster management page.
2. Click on the "Domain management" button to configure your domain.
3. A modal window will appear, providing a field for entering the domain.
4. Enter your domain and click "Save."
5. A sidepage will appear, indicating that the system is processing your request. Please be patient, as this may take up to several minutes.
6. Once the system processes your request, the sidepage will display the data you need to provide to your authoritative DNS provider.

Setting up your DNS provider

You will need to add three records to your DNS provider.

1. Add a TXT record in your DNS provider to validate a domain

The first record is a TXT type record. A TXT record is a specific type of DNS record that contains a text string. These TXT records serve various purposes, and in our case, we use them to verify domain ownership.

To add a TXT record in your DNS provider, follow these steps:

1. Log in to your DNS provider's website or dashboard.
2. Find the section for adding or editing DNS records.
3. Enter the following information for your TXT record: Record type: TXT Name: Copy the value from the Hostname pre-validation TXT name field here Value: Copy the value from the Hostname pre-validation TXT value field here
4. Save changes

2. Adding a CNAME record in your DNS provider to validate a certificate

The second record that you need to add is a CNAME record, which is a type of DNS record that points to another domain or IP address. It is necessary to confirm the certificate.

To add a CNAME record in your DNS provider, follow these steps:

1. Log in to your DNS provider's website or dashboard.
2. Find the section for adding or editing DNS records.
3. Enter the following information for your CNAME record: Record type: CNAME Name: Copy the value from the Certificate pre-validation CNAME name field here Value: Copy the value from the Certificate pre-validation CNAME value field here
4. Save changes

3. Adding a CNAME record in your DNS provider to redirect the traffic

The third record that you need to add is a CNAME record, which is a type of DNS record that points to another domain or IP address. It is required to direct traffic from your hostname to the cluster.

Before you proceed with this step, you need to wait for both records to have an "Active" status. This may take from a few minutes to several hours. You can track the status on the sidepage.

When both statuses are "Active," data for the third record will become enabled on the sidepage.

To add a CNAME record in your DNS provider, follow these steps:

1. Log in to your DNS provider's website or dashboard.
2. Find the section for adding or editing DNS records.
3. Enter the following information for your CNAME record: Record type: CNAME Name: Specify the subdomain that will point to your application. Keep in mind that you cannot use the full domain name due to limitations. For example, if you have the "example.com” domain, you cannot use it, but you can use subdomains like "foo.example.com" or "bar.example.com" instead Value: Copy the value from the Value field on sidepage here
4. Save changes

For the redirect to work, the CNAME record needs to propagate in your DNS provider, which may take a few minutes to several hours. After this, your users will be able to use the application in the cluster.

Changing the domain

To change the bound domain, follow these steps:

1. Click on the pencil icon next to the current domain name on the "Domain Management" sidepage.
2. Please be aware that changing the domain will result in the complete removal of all data associated with the current domain.
3. After changing the domain, you will need to follow the steps described above for domain validation and redirect.

Unlinking the domain

To unlink the domain from your cluster, click on the Remove icon near the domain name on the "Domain Management" sidepage. Please note that unlinking the domain will result in the complete removal of all data associated with it.

What is a Kubernetes (K8s) config file? - FAQ

You can download the K8s config file on this page from the top right of the page by clicking the DOWNLOAD CONFIG FILE button.

A Kubernetes cluster configuration file, often referred to as a kubeconfig file, is a YAML file that contains information about how to connect to and authenticate with a Kubernetes cluster. The kubeconfig file specifies the cluster, user, and context information required to access the Kubernetes API server and interact with the cluster.

The configuration file contains the following information:

1. Cluster information: The address, certificate authority, and other cluster-specific information required to connect to the Kubernetes cluster.
2. User information: The authentication information required to access the Kubernetes cluster, including the user's client certificate and private key.
3. Context information: The context information specifies the user, cluster, and namespace to use when accessing the Kubernetes cluster.

The kubeconfig file is used by the kubectl command-line tool and other Kubernetes clients to interact with the cluster. By default, kubectl looks for the kubeconfig file in the user's home directory under the .kube directory. However, you can specify a different location for the configuration file using the --kubeconfig flag.

The kubeconfig file is an essential component of Kubernetes administration and allows users to manage multiple clusters from a single command-line interface. It is also used in automation scripts and tools that interact with the Kubernetes API server.

Actions you can perform on the page

Kubernetes version upgrade

We are pleased to offer Kubernetes version upgrades for our managed Kubernetes clusters, allowing you to keep your cluster up to date with the latest features and security patches.

When a newer version of Kubernetes becomes available, a 'Change' link will appear next to the Kubernetes version on the cluster page. Hovering over it will show you the available upgrade versions.

To request an upgrade, click on the ‘Change’ link. This will open a side page with a ticket to our tech support. When submitting a ticket, please provide the following information

• The name of your cluster
• The preferred Kubernetes version

Upon receiving your request, we will initiate the upgrade process. Please note that during the upgrade, your cluster will be temporarily unavailable. We will collaborate with you to minimize the impact on your applications.

Once the upgrade is complete, we will notify you, and you can verify that your cluster is running the new version.

Editing the cluster

To edit your cluster, navigate to the page of the specific cluster you wish to modify. Once there, locate the "EDIT CLUSTER" button positioned at the top of the page. Click on this button to make changes to your cluster settings.

Adding nodes to the cluster

If you need to increase the computational resources of the cluster, you can add nodes. To do this, click on the "Add node" tile. Next, choose the required configuration from the list and click on the "Add node" button. Changes in the cluster composition will be reflected on the editing page. If you want to add multiple copies of the same node to the cluster, you can modify the counter on the new node's tile. Please note that the maximum number of nodes in the cluster is 16.

Delete a node from the cluster

If you want to remove an underutilized node from the cluster, click on the "Delete" control on the node's tile.

Change the new node’s name

You have the option to change the name of any new node you wish to add to the cluster on the editing page. To do this, click on the name editing icon and enter the new name for the node.

Manage autoscaling groups

You have the capability to adjust various parameters, such as node configurations or limits. You can create new autoscaling groups or remove existing ones based on your requirements. For detailed guidance on autoscaling groups, please refer to the documentation.

Apply changes to the cluster

Before making any changes to your Kubernetes cluster, it's important to ensure that you have a backup of your existing configuration, in case you need to revert back to the previous state. Additionally, it's important to carefully review any changes you make to ensure that they don't cause unintended consequences or break any dependencies in your cluster.

To apply changes, click on the "Edit cluster" button at the bottom of the page. During the changes, the cluster status will change to ENV_DEVELOPMENT. Nodes undergoing changes will be displayed in the BUSY status. When the changes are successfully applied, the cluster will transition to the ACTIVE status, and nodes will be in the ON status.

If you encounter any issues during changes, please contact technical support.

Please note that you cannot make changes to the cluster deployment area, cluster name, or Kubernetes version using the "Edit cluster" button. To update the Kubernetes version, please use the "Change" link near the cluster version in the top panel with general cluster information on the cluster page.