Change a cluster configuration¶
After deploying a managed cluster, you can configure a few cluster settings using the Container Cloud web UI as described below.
To change a cluster configuration:
Log in to the Container Cloud web UI with the
m:kaas:namespace@operator
orm:kaas:namespace@writer
permissions.Select the required project.
On the Clusters page, click the More action icon in the last column of the required cluster and select Configure cluster.
In the Configure cluster window:
In the General Settings tab, you can:
Add or update proxy for a cluster by selecting the name of previously created proxy settings from the Proxy drop-down menu. To add or update proxy parameters:
In the Proxies tab, configure proxy:
Click Add Proxy.
In the Add New Proxy wizard, fill out the form with the following parameters:
¶ Parameter
Description
Proxy Name
Name of the proxy server to use during cluster creation.
Region Removed in 2.26.0 (16.1.0 and 17.1.0)
From the drop-down list, select the required region.
HTTP Proxy
Add the HTTP proxy server domain name in the following format:
http://proxy.example.com:port
- for anonymous accesshttp://user:password@proxy.example.com:port
- for restricted access
HTTPS Proxy
Add the HTTPS proxy server domain name in the same format as for HTTP Proxy.
No Proxy
Comma-separated list of IP addresses or domain names. For vSphere-based clusters, mandatory to add
host[:port]
of the vCenter server.For implementation details, see Proxy and cache support.
If your proxy requires a trusted CA certificate, select the CA Certificate check box and paste a CA certificate for a MITM proxy to the corresponding field or upload a certificate using Upload Certificate.
Using the SSH Keys drop-down menu, select the required previously created SSH key to add it to the running cluster. If required, you can add several keys or remove unused ones, if any.
Note
To delete an SSH key, use the SSH Keys tab of the main menu.
Applies since Cluster releases 12.5.0 and 11.5.0. Using the Container Registry drop-down menu, select the previously created Docker container registry name to add it to the running cluster.
Applies since Cluster releases 17.0.0, 16.0.0, and 14.1.0. Using the following options, define the maximum number of worker machines to be upgraded in parallel during cluster update:
- Parallel Upgrade Of Worker Machines
The maximum number of the worker nodes to update simultaneously. It serves as an upper limit on the number of machines that are drained at a given moment of time. Defaults to
1
.- Parallel Preparation For Upgrade Of Worker Machines
The maximum number of worker nodes being prepared at a given moment of time, which includes downloading of new artifacts. It serves as a limit for the network load that can occur when downloading the files to the nodes. Defaults to
50
.
In the Stacklight tab, select or deselect StackLight and configure its parameters if enabled.
You can also update the default log level severity for all StackLight components as well as set a custom log level severity for specific StackLight components. For details about severity levels, see Log verbosity.
Click Update to apply the changes.