Releases: loft-sh/vcluster
v0.4.1
Changes
- cli: Improved waiting output of DevSpace running in a pipeline
- cli: New flag
--delete-namespace
to delete the vcluster namespace invcluster delete
(#126) - syncer: Fixed an issue where issued service account tokens would fail the token review api
- syncer: Replace pod host names that have a
.
with-
(#131)
v0.4.1-beta.0
Changes
- cli: Improved waiting output of DevSpace running in a pipeline
- cli: New flag
--delete-namespace
to delete the vcluster namespace invcluster delete
(#126) - syncer: Fixed an issue where issued service account tokens would fail the token review api
- syncer: Replace pod host names that have a
.
with-
(#131)
v0.4.0
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 versionnetworking.k8s.io/v1beta1
is still available and used if nov1
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 forvcluster connect
to start portforwarding with a specific address locally - cli: Updated k3s versions
- cli: New
--upgrade
flag forvcluster create
to disable automatic upgrading of a vcluster if it already exists - build: Fixed an issue where arm64 vcluster docker image contained amd64 binaries
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 versionnetworking.k8s.io/v1beta1
is still available and used if nov1
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 forvcluster connect
to start portforwarding with a specific address locally - cli: Updated k3s versions
- cli: New
--upgrade
flag forvcluster create
to disable automatic upgrading of a vcluster if it already exists - build: Fixed an issue where arm64 vcluster docker image contained amd64 binaries
v0.4.0-beta.2
Support for Kubernetes v1.22
vcluster now officially supports Kubernetes v1.22 as host cluster. However, since k3s does not support it yet, you can only start vcluster on a host cluster with version v1.22, but not actually start vcluster with version v1.22 yet (we'll add that as soon as k3s gets released for v1.22).
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 versionnetworking.k8s.io/v1beta1
is still available and used if nov1
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 forvcluster connect
to start portforwarding with a specific address locally - cli: Updated k3s versions
v0.4.0-beta.1
Merge pull request #118 from FabianKramm/main fix: fixed persistent volume cleanup & --address
v0.3.3
v0.3.3-beta.0
v0.3.2
Changes
- cli: Fixed an issue where
vcluster connect --server
would sometimes not correctly prependhttps://
- cli: New
--connect
flag forvcluster create
that directly runsvcluster connect
after creating the vcluster (#81) - syncer: New flag
--service-namespace
to specify where the vcluster service is available - syncer: Fixed several issues where using
--target-namespace
would not work correctly - syncer: New
--out-kube-config-secret-namespace
flag to override the namespace where vcluster will store the generated kube config (#82) - syncer: New
--out-kube-config-server
flag to override the server of the generated kube config (#84) - syncer: Set owner reference to generated kube config secret if it is in the same namespace as owning statefulset (#83)
v0.3.2-beta.0
Changes
- cli: New
--connect
flag forvcluster create
that directly runsvcluster connect
after creating the vcluster (#81) - syncer: New flag
--service-namespace
to specify where the vcluster service is available - syncer: Fixed several issues where using
--target-namespace
would not work correctly - syncer: New
--out-kube-config-secret-namespace
flag to override the namespace where vcluster will store the generated kube config (#82) - syncer: New
--out-kube-config-server
flag to override the server of the generated kube config (#84) - syncer: Set owner reference to generated kube config secret if it is in the same namespace as owning statefulset (#83)