The v0.23 release of vCluster introduces powerful new capabilities for syncing resources from the host cluster, including secrets, configMaps, and namespaced custom resources. Additionally, this update brings support for Kubernetes v1.32 and several key improvements for stability and usability. Let’s dive in!

fromHost resource syncing

Perhaps the most integral feature of vCluster is syncing resources to and from the host cluster. Our team has been focusing on making consistent progress in this area to provide functionality that will help our users the most. With v0.23 three new resources can be synced from the host cluster to the virtual cluster: secrets, configMaps, and namespaced custom resources.

While cluster-scoped custom resources can already be synced today, they provided limited functionality. The ability to create and sync any namespaced custom resource opens up many new use cases and integrations. Similarly, the ability to sync secrets or configMaps from separate host namespaces into your virtual cluster allows expanded configuration and deployment options.

See the example vcluster.yaml below showing how to sync:

1. Secrets from namespace foo in the host cluster to namespace bar in the virtual cluster

2. Custom resources example.demo.vcluster.com from host namespace to the default namespace in the virtual cluster

sync:
  fromHost:
    secrets:
      enabled: true
      mappings:
        byName:
          # syncs all Secrets from "foo" namespace
          # to the "bar" namespace in a virtual cluster. Secret names are unchanged.
          "foo/*": "bar/*"
    customResources:
      example.demo.vcluster.com:
	      enabled: true
	      mappings:
	        byName:
            # syncs all `example` objects from vCluster host namespace
            # to the "default" namespace in the virtual cluster
            "": "default"

For more information, see the docs on ConfigMaps, Secrets, and Custom Resources.

Support for Kubernetes v1.32

In this release, we’ve also added support for Kubernetes v1.32, enabling users to take advantage of the latest enhancements, security updates, and performance improvements in the upstream Kubernetes release. However, please be aware that this update does not extend to k0s.

Notable Improvements

• Intermittent connection interruptions between virtual clusters and their platform will not disrupt the usage of pro features, and will be handled more gracefully.

• PriorityClass can now be automatically applied to workloads.

Other Changes

• Please note that any Node objects created on the virtual cluster will no longer be automatically removed, and must be manually cleaned up.

• Deploying multiple virtual clusters per-namespace is now deprecated. When it is detected, the following will occur:

  • When using v0.23 a warning will be logged

  • When using v0.24 the virtual cluster pod will not start unless you enable the reuseNamespace option in your vCluster’s config.yaml

  • In v0.25 this functionality will no longer be supported, the reuseNamespace option will be removed, and the virtual cluster pod will no longer start.

For a list of additional fixes and smaller changes, please refer to the release notes.