Skip to main content
Version: v0.29 Stable

Deploy changes in configuration options

Deploy changes for control plane running as a container​

Limited vCluster Tenancy Configuration Support

This feature is only available for the following:

Running the control plane as a container and the following worker node types:
  • Host Nodes
  • Private Nodes

You can always introduce or update your vcluster.yaml and deploy new configuration options.

The vCluster control plane pod is going to be re-deployed.

Limitations on changing configuration

You cannot change distros once a virtual cluster is deployed, with one exception: starting with vCluster 0.25.0, migration from K3s to K8s distro is supported. For more details, see the K3s to K8s migration guide.

vCluster CLI Version

To keep the same version of your vCluster, your CLI needs to be the same version as your virtual cluster.

vcluster create --upgrade <VCLUSTER_NAME> -n <VCLUSTER_NAMESPACE> -f vcluster.yaml

Replace:

  • <VCLUSTER_NAME> with the name of the vCluster instance to update.
  • <VCLUSTER_NAMESPACE> with the namespace where the vCluster instance is deployed.

Deploy changes for vCluster Standalone​

Limited vCluster Tenancy Configuration Support

This feature is only available for the following:

Running the control plane as a binary for vCluster Standalone, which uses private nodes.

Changing the vcluster.yaml configuration has to be done on all control plane nodes.

  1. Modify the vcluster.yaml.

    The vcluster.yaml is located at: /etc/vcluster/vcluster.yaml. Edit and save your changes.

  2. Restart vCluster systemD service to deploy your changes.

    Restart vCluster
    systemctl restart vcluster.service