Releases: loft-sh/vcluster
v0.4.4
Changes
- syncer: Annotations are now merged with the host cluster annotations on objects instead of always overriding them.
- syncer: New
--set-owner
flag that will figure out automatically the owning object of the vcluster pod and set that to the vcluster created objects (#181) - syncer: Deprecated the flag
--owning-statefulset
- syncer: vcluster now automatically adds the autoscaler annotation
cluster-autoscaler.kubernetes.io/safe-to-evict
for pods that are deployed with a deployment, replicaset or statefulset within the vcluster to signal autoscalers that it is safe to evict those pods. - cli: improve
vcluster connect
and make the command work without requiring a statefulset
v0.4.4-beta.1
Changes
- syncer: Annotations are now merged with the host cluster annotations on objects instead of always overriding them.
- syncer: New
--set-owner
flag that will figure out automatically the owning object of the vcluster pod and set that to the vcluster created objects (#181) - syncer: Deprecated the flag
--owning-statefulset
- syncer: vcluster now automatically adds the autoscaler annotation
cluster-autoscaler.kubernetes.io/safe-to-evict
for pods that are deployed with a deployment, replicaset or statefulset within the vcluster to signal autoscalers that it is safe to evict those pods. - cli: improve
vcluster connect
and make the command work without requiring a statefulset
v0.4.3
Changes
- Fixed an issue where the hostname of pods created from a statefulset were wrong (thanks @moustafab)
v0.4.2
Changes
- cli: Updated k3s versions
- cli: New
--output
flag invcluster list
(thanks @jzbruno) - cli: Use helm executable path for
helm version
invcluster create
(thanks @developer-guy) - cli: vcluster will now restart port-forwarding automatically if it loses connection to the pod
- syncer: Rename the annotation
vcluster.loft.sh/translate-pv
tovcluster.loft.sh/skip-translate
v0.4.2-beta.1
Changes
- cli: Updated k3s versions
- cli: New
--output
flag invcluster list
(thanks @jzbruno) - cli: Use helm executable path for
helm version
invcluster create
(thanks @developer-guy) - cli: vcluster will now restart port-forwarding automatically if it loses connection to the pod
- syncer: Rename the annotation
vcluster.loft.sh/translate-pv
tovcluster.loft.sh/skip-translate
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