v0.4.0-beta.3

Support for Kubernetes v1.22

vcluster now officially supports Kubernetes v1.22 as host cluster.

Bi-Directional Sync for Persistent Volumes (#102)

vcluster does now support creating custom persistent volumes within vcluster that will be synced to the host cluster. This allows you to manage persistent volumes directly within a vcluster. Please take a look at the vcluster docs for more information.

Other Changes

• syncer: Support added for ingress sync with version networking.k8s.io/v1. The old version networking.k8s.io/v1beta1 is still available and used if no v1 is supported in the host cluster (pre Kubernetes v1.19) (#64)
• syncer: Fixed an issue where terminating pods wouldn't get cleaned up correctly if the service account was deleted beforehand (#119)
• syncer: Fixed several instances where secret names where not correctly translated in volume definitions (#103)
• cli: New --address flag for vcluster connect to start portforwarding with a specific address locally
• cli: Updated k3s versions
• cli: New --upgrade flag for vcluster create to disable automatic upgrading of a vcluster if it already exists
• build: Fixed an issue where arm64 vcluster docker image contained amd64 binaries