loft-sh/loft v4.0.0-beta.1 on GitHub

Highlights

Deploy vCluster your way

Deploy vCluster with your existing tools like Argo CD without requiring a Platform Agent to be installed in the host cluster. Externally deployed instances will now connect and register directly with the Platform after running the vCluster CLI command: vcluster add vcluster VCLUSTER_NAME

Alternatively, configure the Platform secret in the vcluster.yaml configuration file:

external:
  platform:
    apiKey:
      secretName: "vcluster-platform-api-key"
      namespace: "" # empty defaults to the Helm release namespace

The Platform now supports multiple vCluster deployment types:

Deployed by Platform, managed by Platform.
Deployed by Helm, managed by Platform with Platform Agent on host cluster.
Deployed by Helm, managed by Platform without a Platform Agent on host cluster.

Platform capabilities by deployed type

Deployment Type	vCluster Pro Features	User Access	Sleep Mode	Editing Config	Project Quotas	Rancher Integration	Argo CD Integration	Apps	Host Namespace Mgmt	Multi-region mode	Isolated Control Plane	Platform Secrets
Deployed by Platform, managed by Platform	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
Deployed by Helm, managed by Platform with Platform Agent on host cluster	✅	✅	✅	optional	✅	✅	✅	✅	✅	✅	✅	✅
Deployed by Helm, managed by Platform without a Platform Agent on host cluster	✅	✅	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌

Support for vCluster v0.20

Now you can use the latest vCluster version v0.20.0-beta together with the Platform v4.0.0-beta capabilities and activate vCluster Pro features.

Migrating vCluster from v0.19 to v0.20

The Platform automatically attempts to convert existing vCluster v0.19 values to the new v0.20 vcluster.yaml configuration file when upgrading it via the UI. This is in addition to the vCluster v0.20 CLI command you can run to convert pre-v0.19 values: vcluster convert config --distro k3s -f VALUES_FILE > vcluster.yaml

Redesigned vCluster UI editor

The new vCluster UI editor brings together configuration, cluster resource visibility and audit logs into one full page view.
vCluster v0.20 instances display a new vcluster.yaml viewer and editor to make it easier to configure with validation and auto-complete.
"Spaces" has been renamed to "Host Namespaces" for clarity, however, functionality remains the same as Platform v3.4

Other Changes

vCluster v0.20.x is now the default version when creating virtual clusters via the Platform.
Offline virtual clusters without an Agent on the host cluster are automatically deregistered and removed from the Platform after 24 hours of being disconnected from the Platform.
Added a status filter to the Namespaces product page, formally called "Spaces".

Breaking Changes

Project namespaces: The default namespace prefix changed from loft-p- to just p-.
Note: Existing Platform users need to explicitly set this configuration to projectNamespacePrefix: loft-p- in the Platform configuration when upgrading or re-installing from pre-v4 to v4 to ensure the existing namespace prefix is maintained.
Isolated Control Plane: Isolated Control plane configuration moved from the Platform to the vcluster.yaml configuration file under experimental.isolatedControlPlane.
Spaces: Existing users of the Loft Spaces product need to use the vCluster v0.20 CLI in conjunction with this Platform v4.0.0-beta release.
Removed APIs: virtualclusters.cluster.loft.sh and spaces.cluster.loft.sh
Externally deployed: Externally deployed virtual clusters now have a spec.external boolean field on the VirtualClusterInstance CRD instead of the previous loft.sh/skip-helm-deploy annotation.

Deprecations

Loft CLI: The Loft CLI is now deprecated. The majority of commands have been migrated to the vCluster v0.20 CLI.
Auto-import: Automatically importing via annotation is no longer supported. Virtual clusters can be automatically imported by configuring the external.platform.apiKey.secretName or by creating them via the vCluster CLI while logged into the platform vcluster create VCLUSTER_NAME --driver platform.

Upgrading

Ensure that you have upgraded first to v3 before attempting to upgrade to v4
Existing virtual clusters cannot have their vCluster version modified via the UI at the moment. This will be enabled in a subsequent release. However, upgrading from v0.19 to v0.20 is currently possible via the vCluster list page within the "vCluster Version" column.
Upgrading from Platform v3 to v4 is only possible with vCluster v0.20 CLI. The UI will support upgrading in a future release.

View upgrade guide

Full Changelog

https://github.com/loft-sh/loft-enterprise/compare/v4.0.0-alpha.19...v4.0.0-alpha.20