Releases: loft-sh/vcluster
v0.5.3-beta.0
Changes
- syncer: Fixed an issue where vcluster would incorrectly route pod exec, attach and port-forwarding admission requests
v0.6.0-alpha.5
Pause and Resume vclusters
vcluster is now able to pause and resume. Pausing a vcluster means to temporarily scale down the vcluster and delete all its created workloads on the host cluster. This can be useful to save computing resources used by vcluster workloads in the host cluster.
For more information please checkout the vcluster docs
Expiring kube configs & automatic service account creation
vcluster is now able to automatically create service account tokens for generated kube configs, which allow you to easily create kube configs for other vcluster users that should not be cluster admin. For example:
# Create a kube config for a cluster viewer
vcluster connect my-vcluster -n my-vcluster --service-account viewer --cluster-role view
# OR: create a kube config for a cluster admin
vcluster connect my-vcluster -n my-vcluster --service-account admin --cluster-role cluster-admin
# OR: create a kube config that expires after an hour
vcluster connect my-vcluster -n my-vcluster --service-account viewer --cluster-role view --token-expiration 3600
This makes it also possible to use vcluster more easily without ingresses that require ssl passthrough. For more information please checkout the vcluster access docs and vcluster ingress docs
Support for VolumeSnapshots
vcluster now supports syncing of volume snapshots between the host and virtual cluster, that can be enabled via a values.yaml
:
rbac:
clusterRole:
enabled: true
role:
extended: true
syncer:
extraArgs:
- --sync=volumesnapshots
and then used via:
vcluster create ... -f values.yaml
Other Changes
- cli: New flag
--insecure
forvcluster connect
to create a kube config withinsecure-skip-tls-verify
- cli: Notify the user about incompatible workdir file when running
vcluster create
- cli: Add v1.23 support for k3s
- syncer: Start controllers after api server started
- syncer: Fixed syncer cache race condition after Service creation
- chart: Fixed a problem where k3s would not startup correctly on cgroupsv2 nodes (#264)
- other: For each release there will be a new
vcluster-images.txt
which holds all the needed images by vcluster. In addition, we include two scripts to download and push the needed images automatically
v0.6.0-alpha.4
Pause and Resume vclusters
vcluster is now able to pause and resume. Pausing a vcluster means to temporarily scale down the vcluster and delete all its created workloads on the host cluster. This can be useful to save computing resources used by vcluster workloads in the host cluster.
For more information please checkout the vcluster docs
Expiring kube configs & automatic service account creation
vcluster is now able to automatically create service account tokens for generated kube configs, which allow you to easily create kube configs for other vcluster users that should not be cluster admin. For example:
# Create a kube config for a cluster viewer
vcluster connect my-vcluster -n my-vcluster --service-account viewer --cluster-role view
# OR: create a kube config for a cluster admin
vcluster connect my-vcluster -n my-vcluster --service-account admin --cluster-role cluster-admin
# OR: create a kube config that expires after an hour
vcluster connect my-vcluster -n my-vcluster --service-account viewer --cluster-role view --token-expiration 3600
This makes it also possible to use vcluster more easily without ingresses that require ssl passthrough. For more information please checkout the vcluster access docs and vcluster ingress docs
Support for VolumeSnapshots
vcluster now supports syncing of volume snapshots between the host and virtual cluster, that can be enabled via a values.yaml
:
rbac:
clusterRole:
enabled: true
role:
extended: true
syncer:
extraArgs:
- --sync=volumesnapshots
and then used via:
vcluster create ... -f values.yaml
Other Changes
- cli: New flag
--insecure
forvcluster connect
to create a kube config withinsecure-skip-tls-verify
- cli: Notify the user about incompatible workdir file when running
vcluster create
- cli: Add v1.23 support for k3s
- syncer: Start controllers after api server started
- syncer: Fixed syncer cache race condition after Service creation
- chart: Fixed a problem where k3s would not startup correctly on cgroupsv2 nodes (#264)
- other: For each release there will be a new
vcluster-images.txt
which holds all the needed images by vcluster. In addition, we include two scripts to download and push the needed images automatically
v0.5.2
v0.5.2-beta.2
Changes
- Added support for k3s v1.22 & v1.23
- Fixed an issue where k3s wouldn't start correctly (#264)
- Fixed syncer cache race condition after Service creation
v0.5.2-beta.1
Changes
- Added support for k3s v1.22 & v1.23
- Fixed an issue where k3s wouldn't start correctly (#264)
v0.6.0-alpha.3
Pause and Resume vclusters
vcluster is now able to pause and resume. Pausing a vcluster means to temporarily scale down the vcluster and delete all its created workloads on the host cluster. This can be useful to save computing resources used by vcluster workloads in the host cluster.
For more information please checkout the vcluster docs
Expiring kube configs & automatic service account creation
vcluster is now able to automatically create service account tokens for generated kube configs, which allow you to easily create kube configs for other vcluster users that should not be cluster admin. For example:
# Create a kube config for a cluster viewer
vcluster connect my-vcluster -n my-vcluster --service-account viewer --cluster-role view
# OR: create a kube config for a cluster admin
vcluster connect my-vcluster -n my-vcluster --service-account admin --cluster-role cluster-admin
# OR: create a kube config that expires after an hour
vcluster connect my-vcluster -n my-vcluster --service-account viewer --cluster-role view --token-expiration 3600
This makes it also possible to use vcluster more easily without ingresses that require ssl passthrough. For more information please checkout the vcluster access docs and vcluster ingress docs
Support for VolumeSnapshots
vcluster now supports syncing of volume snapshots between the host and virtual cluster, that can be enabled via a values.yaml
:
rbac:
clusterRole:
enabled: true
role:
extended: true
syncer:
extraArgs:
- --sync=volumesnapshots
and then used via:
vcluster create ... -f values.yaml
Other Changes
- cli: New flag
--insecure
forvcluster connect
to create a kube config withinsecure-skip-tls-verify
- cli: Add v1.23 support for k3s
- syncer: Start controllers after api server started
- chart: Fixed a problem where k3s would not startup correctly on cgroupsv2 nodes (#264)
- other: For each release there will be a new
vcluster-images.txt
which holds all the needed images by vcluster. In addition, we include two scripts to download and push the needed images automatically
v0.6.0-alpha.2
Pause and Resume vclusters
vcluster is now able to pause and resume. Pausing a vcluster means to temporarily scale down the vcluster and delete all its created workloads on the host cluster. This can be useful to save computing resources used by vcluster workloads in the host cluster.
For more information please checkout the vcluster docs
Expiring kube configs & automatic service account creation
vcluster is now able to automatically create service account tokens for generated kube configs, which allow you to easily create kube configs for other vcluster users that should not be cluster admin. For example:
# Create a kube config for a cluster viewer
vcluster connect my-vcluster -n my-vcluster --service-account viewer --cluster-role view
# OR: create a kube config for a cluster admin
vcluster connect my-vcluster -n my-vcluster --service-account admin --cluster-role cluster-admin
# OR: create a kube config that expires after an hour
vcluster connect my-vcluster -n my-vcluster --service-account viewer --cluster-role view --token-expiration 3600
This makes it also possible to use vcluster more easily without ingresses that require ssl passthrough. For more information please checkout the vcluster access docs and vcluster ingress docs
Support for VolumeSnapshots
vcluster now supports syncing of volume snapshots between the host and virtual cluster, that can be enabled via a values.yaml
:
rbac:
clusterRole:
enabled: true
role:
extended: true
syncer:
extraArgs:
- --sync=volumesnapshots
and then used via:
vcluster create ... -f values.yaml
Other Changes
- cli: New flag
--insecure
forvcluster connect
to create a kube config withinsecure-skip-tls-verify
- cli: Removed k3s v1.22 support as it currently breaks on startup
- other: For each release there will be a new
vcluster-images.txt
which holds all the needed images by vcluster. In addition, we include two scripts to download and push the needed images automatically
v0.5.1
v0.5.1-beta.2
Changes
- cli: Removed k3s v1.22 support until #264 is fixed
- syncer: Wait for api server before starting controllers