vCluster - Create fully functional virtual Kubernetes clusters - Each vcluster runs inside a namespace of the underlying k8s cluster. It's cheaper than creating separate full-blown clusters and it offers better multi-tenancy and isolation than regular namespaces.
We've streamlined the deployment process by consolidating all different vCluster Helm charts (vcluster, vcluster-k8s, vcluster-k0s, and vcluster-eks) into a single, unified chart. This change is designed to simplify management and upgrading of virtual clusters:
controlPlane:
distro:
k8s:
enabled: true
vcluster.yaml configuration & docsWe're excited to introduce the new vcluster.yaml file, replacing the previous Helm values.yaml. This new configuration features a completely revamped format designed to enhance the user experience:
vcluster convert config command makes it easy to transition to the new vcluster.yaml format.vcluster.yaml, making it easier to cross-reference settings within the file and corresponding sections in the docs.
vcluster.yamlIn order to make it easy to convert your old values (pre-v0.20) to the new vcluster.yaml format, you can leverage the new CLI command: vcluster convert config command. For example, let's take these pre-v0.20 configuration values:
service:
type: NodePort
sync:
nodes:
enabled: true
Passing the above old values using the vCluster CLI command vcluster convert config --distro k8s < /path/to/this/file.yaml will generate the following values:
controlPlane:
backingStore:
etcd:
deploy:
enabled: true
distro:
k8s:
enabled: true
service:
spec:
type: NodePort
statefulSet:
scheduling:
podManagementPolicy: OrderedReady
sync:
fromHost:
nodes:
enabled: true
View configuration conversion guide
We changed the default distribution for the vCluster control plane from K3s to K8s. This is the least opinionated option, offering greater flexibility and compatibility:
Embedded SQLite has been set as the default backing store for the K8s distribution. This is to simplify operations and enhance performance for smaller virtual clusters:
Continued Support for etcd: For users with larger deployments or those needing more advanced features, external etcd deployed by vCluster remains a fully supported option:
controlPlane:
distro:
k8s:
enabled: true
backingStore:
etcd:
deploy:
enabled: true
We've updated the default image for vCluster to ghcr.io/loft-sh/vcluster-pro. This change allows users to seamlessly test and adopt vCluster Pro features without disrupting the existing open-source functionality. The Pro features are integrated into the Pro image but remain inactive by default to ensure that your experience remains consistent with the open-source version unless you specifically activate Pro features.
For users who prefer using the open-source image, simply adjust your vcluster.yaml configuration to use ghcr.io/loft-sh/vcluster-oss:
controlPlane:
statefulSet:
image:
repository: ghcr.io/loft-sh/vcluster-oss
Pre-v0.20.0-beta.1, when you enabled syncing Ingresses from the virtual to the host cluster, it would also automatically sync all IngressClasses from the host cluster. However, this required a cluster role which some vCluster users don’t have. We’ve now decoupled these syncing behaviors so you can individually enable syncing Ingresses as well as IngressClasses separately.
sync:
toHost:
ingresses:
enabled: true
fromHost:
ingressClasses:
enabled: true
vcluster create Flags:--disable-ingress-sync
--extra-values
--labels
--annotations
--project
--cluster
--template
--template-version
--link
--params
--set-param
--disable-pro
vcluster delete Flags:--project
vcluster connect Flags:--project
vcluster pause Flags:--project
--prevent-wakeup
vcluster resume Flags:--project
vcluster start Flags:--kube-config-context-name
--sync
--request-header-ca-cert
--client-ca-cert
--server-ca-cert
--server-ca-key
--kube-config
--tls-san
--out-kube-config-secret
--out-kube-config-secret-namespace
--out-kube-config-server
--target-namespace
--service-name
--set-owner
--name
--bind-address
--port
--sync-all-nodes
--enable-scheduler
--disable-fake-kubelets
--fake-kubelet-ips
--node-clear-image-status
--translate-image
--enforce-node-selector
--enforce-toleration
--node-selector
--service-account
--override-hosts
--override-hosts-container-image
--cluster-domain
--leader-elect
--lease-duration
--renew-deadline
--retry-period
--disable-plugins
--plugin-listen-address
--default-image-registry
--enforce-pod-security-standard
--sync-labels
--plugins
--map-virtual-service
--map-host-service
--host-metrics-bind-address
--virtual-metrics-bind-address
--mount-physical-host-paths
--multi-namespace-mode
--namespace-labels
--sync-all-configmaps
--sync-all-secrets
--proxy-metrics-server
--service-account-token-secrets
--rewrite-host-paths
--sync-node-changes
--fake-kubelets
--fake-nodes
--fake-persistent-volumes
--enable-storage-classes
--enable-priority-classes
--suffix
--owning-statefulset
--disable-sync-resources
--pro-license-secret
--remote-kube-config
--remote-namespace
--remote-service-name
--integrated-coredns
--use-coredns-plugin
--noop-syncer
--sync-k8s-service
--etcd-embedded
--migrate-from
--etcd-replicas
--enforce-validating-hook
--enforce-mutating-hook
We changed the vCluster values.yaml format in this release and most old helm values will no longer work. We will provide a migration script that automatically updates the old values to the new ones. You can check the new format at https://github.com/loft-sh/vcluster/blob/main/chart/values.yaml
We merged all different vCluster charts (vcluster, vcluster-k8s, vcluster-k0s & vcluster-eks) into a single helm chart. This should simplify vCluster deployment in the future. We will provide a migration script that automatically updates the old values to the new ones and we added a values schema json to the helm chart that will let upgrading of the chart fail if the values format doesn't match. You can check the new format at https://github.com/loft-sh/vcluster/blob/main/chart/values.yaml
You can enable a specific distro now via the helm chart values:
controlPlane:
distro:
k8s:
enabled: true
We changed the default distro from k3s to k8s as k8s is the least opinionated and you can now also use kine with k8s, which allows to use SQLite and other storage backends with the regular k8s distro to overcome the biggest problem using k8s so far for smaller vClusters.
Currently it was only possible to use external etcd deployed by vCluster or embedded etcd (as a pro feature) with the k8s distro. With v0.20 its also possible to use Kine with the k8s distro and SQLite is the new default for it. You can still use the external etcd deployed by vCluster with:
controlPlane:
distro:
k8s:
enabled: true
backingStore:
etcd:
deploy:
enabled: true
To allow easier trying out of pro features, we changed the default image repository to be ghcr.io/loft-sh/vcluster-pro, which includes besides the oss code extra optional pro features. Pro features need to be enabled manually to have an effect and are all disabled by default, which means only oss code is executed without any extra configuration.
If you want to use the pure oss image, you can use the following configuration:
controlPlane:
statefulSet:
image:
repository: ghcr.io/loft-sh/vcluster-oss
Full Changelog: https://github.com/loft-sh/vcluster/compare/v0.19.5...v0.20.0-alpha.4
We changed the vCluster values.yaml format in this release and most old helm values will no longer work. We will provide a migration script that automatically updates the old values to the new ones. You can check the new format at https://github.com/loft-sh/vcluster/blob/main/chart/values.yaml
We merged all different vCluster charts (vcluster, vcluster-k8s, vcluster-k0s & vcluster-eks) into a single helm chart. This should simplify vCluster deployment in the future. We will provide a migration script that automatically updates the old values to the new ones and we added a values schema json to the helm chart that will let upgrading of the chart fail if the values format doesn't match. You can check the new format at https://github.com/loft-sh/vcluster/blob/main/chart/values.yaml
You can enable a specific distro now via the helm chart values:
controlPlane:
distro:
k8s:
enabled: true
We changed the default distro from k3s to k8s as k8s is the least opinionated and you can now also use kine with k8s, which allows to use SQLite and other storage backends with the regular k8s distro to overcome the biggest problem using k8s so far for smaller vClusters.
Currently it was only possible to use external etcd deployed by vCluster or embedded etcd (as a pro feature) with the k8s distro. With v0.20 its also possible to use Kine with the k8s distro and SQLite is the new default for it. You can still use the external etcd deployed by vCluster with:
controlPlane:
distro:
k8s:
enabled: true
backingStore:
etcd:
deploy:
enabled: true
Full Changelog: https://github.com/loft-sh/vcluster/compare/v0.19.5...v0.20.0-alpha.3
We changed the vCluster values.yaml format in this release and most old helm values will no longer work. We will provide a migration script that automatically updates the old values to the new ones. You can check the new format at https://github.com/loft-sh/vcluster/blob/main/chart/values.yaml
We merged all different vCluster charts (vcluster, vcluster-k8s, vcluster-k0s & vcluster-eks) into a single helm chart. This should simplify vCluster deployment in the future. We will provide a migration script that automatically updates the old values to the new ones and we added a values schema json to the helm chart that will let upgrading of the chart fail if the values format doesn't match. You can check the new format at https://github.com/loft-sh/vcluster/blob/main/chart/values.yaml
You can enable a specific distro now via the helm chart values:
controlPlane:
distro:
k8s:
enabled: true
We changed the default distro from k3s to k8s as k8s is the least opinionated and you can now also use kine with k8s, which allows to use SQLite and other storage backends with the regular k8s distro to overcome the biggest problem using k8s so far for smaller vClusters.
Currently it was only possible to use external etcd deployed by vCluster or embedded etcd (as a pro feature) with the k8s distro. With v0.20 its also possible to use Kine with the k8s distro and SQLite is the new default for it. You can still use the external etcd deployed by vCluster with:
controlPlane:
distro:
k8s:
enabled: true
backingStore:
etcd:
deploy:
enabled: true
Full Changelog: https://github.com/loft-sh/vcluster/compare/v0.19.5...v0.20.0-alpha.2
We changed the vCluster values.yaml format in this release and old helm values will no longer work. We will provide a migration script that automatically updates the old values to the new ones. You can check the new format at https://github.com/loft-sh/vcluster/blob/main/chart/values.yaml
We merged all different vCluster charts (vcluster, vcluster-k8s, vcluster-k0s & vcluster-eks) into a single helm chart. This should simplify vCluster deployment going further. We will provide a migration script that automatically updates the old values to the new ones. You can check the new format at https://github.com/loft-sh/vcluster/blob/main/chart/values.yaml
You can enable a specific distro now via the helm chart values:
controlPlane:
distro:
k8s:
enabled: true
k3s:
enabled: false
k0s:
enabled: false
We changed the default distro from k3s to k8s as k8s is less opinionated and you can now also use kine with k8s, which allows to use SQLite and other storage backends with the regular k8s distro.
Currently it was only possible to use external etcd deployed by vCluster or embedded etcd (as a pro feature) with the k8s distro. With v0.20 its also possible to use Kine with the k8s distro and SQLite is the new default for it. You can still use the external etcd deployed by vCluster with:
controlPlane:
distro:
k8s:
enabled: true
backingStore:
etcd:
deploy:
enabled: true
Full Changelog: https://github.com/loft-sh/vcluster/compare/v0.19.4...v0.20.0-alpha.1
Full Changelog: https://github.com/loft-sh/vcluster/compare/v0.19.4...v0.19.5
We changed the vCluster values.yaml format in this release and old helm values will no longer work. We also merged all vCluster charts into a single helm chart. We will provide a migration script that automatically updates the old values to the new ones. You can check the new format at https://github.com/loft-sh/vcluster/blob/main/chart/values.yaml
Full Changelog: https://github.com/loft-sh/vcluster/compare/v0.19.4...v0.20.0-alpha.0
Full Changelog: https://github.com/loft-sh/vcluster/compare/v0.19.3...v0.19.4
Full Changelog: https://github.com/loft-sh/vcluster/compare/v0.19.2...v0.19.3
Full Changelog: https://github.com/loft-sh/vcluster/compare/v0.19.1...v0.19.2