vCluster - Create fully functional virtual Kubernetes clusters - Each vcluster runs inside a namespace of the underlying k8s cluster. It's cheaper than creating separate full-blown clusters and it offers better multi-tenancy and isolation than regular namespaces.
APACHE-2.0 License
Bot releases are hidden (Show)
Published by matskiv almost 2 years ago
Greatly improved Support for logging and backup solutions
We have added an opt-in feature for vcluster which allows us to support logging solutions like ELK, fluentd, loki etc. deployed inside the vcluster. Along with these we also enable support for backup solutions like velero and VM solutions like kubevirt. These applications mount the host paths such as "/var/log" or "/var/lib/kubelet/pods" to retrieve information about workloads in the cluster. You can ensure that the expected data are made available to these applications by enabling the "Hostpath Mapper" feature of vcluster.
High availability support for k3s with external datastore
vcluster now supports HA for the default k3s distro. This is a new alternative to our existing HA support with the k8s distro of vcluster. However it currently requires an external datastore to be configured. New chapter of the HA documentation page describes how to install vcluster with HA k3s - https://www.vcluster.com/docs/operator/high-availability#k3s
Automatically sync CSI resources when scheduler is enabled.
When vcluster scheduler is enabled, the vcluster will start syncing additional storage-related resources to make correct scheduling decisions. These resources are - CSIStorageCapacity, CSINode, and CSIDriver. You can disable this as described in the documentation.
sync:
hoststorageclasses:
enabled: true
vcluster list
CLI command by @mahendrabagul in https://github.com/loft-sh/vcluster/pull/787
Full Changelog: https://github.com/loft-sh/vcluster/compare/v0.12.3...v0.13.0-beta.1
Published by matskiv almost 2 years ago
Greatly improved Support for logging and backup solutions
We have added an opt-in feature for vcluster which allows us to support logging solutions like ELK, fluentd, loki etc. deployed inside the vcluster. Along with these we also enable support for backup solutions like velero and VM solutions like kubevirt. These applications mount the host paths such as "/var/log" or "/var/lib/kubelet/pods" to retrieve information about workloads in the cluster. You can ensure that the expected data are made available to these applications by enabling the "Hostpath Mapper" feature of vcluster.
High availability support for k3s with external datastore
vcluster now supports HA for the default k3s distro. This is a new alternative to our existing HA support with the k8s distro of vcluster. However it currently requires an external datastore to be configured. New chapter of the HA documentation page describes how to install vcluster with HA k3s - https://www.vcluster.com/docs/operator/high-availability#k3s
Automatically sync CSI resources when scheduler is enabled.
When vcluster scheduler is enabled, the vcluster will start syncing additional storage-related resources to make correct scheduling decisions. These resources are - CSIStorageCapacity, CSINode, and CSIDriver. You can disable this as described in the documentation.
sync:
hoststorageclasses:
enabled: true
vcluster list
CLI command by @mahendrabagul in https://github.com/loft-sh/vcluster/pull/787
Full Changelog: https://github.com/loft-sh/vcluster/compare/v0.12.3...v0.13.0-beta.0
Published by matskiv almost 2 years ago
Full Changelog: https://github.com/loft-sh/vcluster/compare/v0.12.2...v0.12.3-beta.0
Published by matskiv almost 2 years ago
Greatly improved Support for logging and backup solutions
We have added an opt-in feature for vcluster which allows us to support logging solutions like ELK, fluentd, loki etc. deployed inside the vcluster. Along with these we also enable support for backup solutions like velero and VM solutions like kubevirt. These applications mount the host paths such as "/var/log" or "/var/lib/kubelet/pods" to retrieve information about workloads in the cluster. You can ensure that the expected data are made available to these applications by enabling the "Hostpath Mapper" feature of vcluster.
vcluster list
CLI command by @mahendrabagul in https://github.com/loft-sh/vcluster/pull/787
Full Changelog: https://github.com/loft-sh/vcluster/compare/v0.12.2...v0.13.0-alpha.0
Published by FabianKramm almost 2 years ago
Full Changelog: https://github.com/loft-sh/vcluster/compare/v0.12.2...v0.12.3-beta.0
Published by FabianKramm about 2 years ago
Full Changelog: https://github.com/loft-sh/vcluster/compare/v0.12.1...v0.12.2
Published by FabianKramm about 2 years ago
sync.ingresses
is enabled by @felipecrs in https://github.com/loft-sh/vcluster/pull/768
Full Changelog: https://github.com/loft-sh/vcluster/compare/v0.12.0...v0.12.1
Published by FabianKramm about 2 years ago
sync.ingresses
is enabled by @felipecrs in https://github.com/loft-sh/vcluster/pull/768
Full Changelog: https://github.com/loft-sh/vcluster/compare/v0.12.0...v0.12.1-beta.0
Published by FabianKramm about 2 years ago
vcluster will by default now not sync ingresses anymore. If you require ingress sync, please make sure to set:
sync:
ingresses:
enabled: true
Full Changelog: https://github.com/loft-sh/vcluster/compare/v0.11.2...v0.12.0
Published by FabianKramm about 2 years ago
vcluster will by default now not sync ingresses anymore. If you require ingress sync, please make sure to set:
sync:
ingresses:
enabled: true
Full Changelog: https://github.com/loft-sh/vcluster/compare/v0.11.2...v0.12.0-beta.1
Published by FabianKramm about 2 years ago
vcluster will by default now not sync ingresses anymore. If you require ingress sync, please make sure to set:
sync:
ingresses:
enabled: true
Full Changelog: https://github.com/loft-sh/vcluster/compare/v0.11.2...v0.12.0-beta.0
Published by FabianKramm about 2 years ago
vcluster will by default now not sync ingresses anymore. If you require ingress sync, please make sure to set:
sync:
ingresses:
enabled: true
in the helm chart from now on.
Full Changelog: https://github.com/loft-sh/vcluster/compare/v0.11.2...v0.12.0-alpha.0
Published by FabianKramm about 2 years ago
ingressClassName
to the ingress example by @hariprasadiit in https://github.com/loft-sh/vcluster/pull/658
Full Changelog: https://github.com/loft-sh/vcluster/compare/v0.11.1...v0.11.2
Published by FabianKramm about 2 years ago
Full Changelog: https://github.com/loft-sh/vcluster/compare/v0.11.1...v0.11.2-beta.0
Published by FabianKramm about 2 years ago
--background-proxy
in vcluster connect
to start port-forwarding in a docker container in the background by @tukobadnyanoba in https://github.com/loft-sh/vcluster/pull/662
Full Changelog: https://github.com/loft-sh/vcluster/compare/v0.11.1...v0.11.2-alpha.0
Published by FabianKramm about 2 years ago
/etc
folder instead of just /etc/rancher
pods/ephemeralContainers
and pods/status
permissions to false by default. Added new sync.pods.ephemeralContainers
and sync.pods.status
option to enable those permissions.vcluster connect
in minikube vm scenariovcluster list
had the wrong formatPublished by FabianKramm about 2 years ago
/etc
folder instead of just /etc/rancher
pods/ephemeralContainers
and pods/status
permissions to false by default. Added new sync.pods.ephemeralContainers
and sync.pods.status
option to enable those permissions.vcluster connect
in minikube vm scenariovcluster list
had the wrong formatPublished by FabianKramm about 2 years ago
/etc
folder instead of just /etc/rancher
Published by FabianKramm about 2 years ago
We removed the deprecated kubernetes.io/ingress.class
annotation from the ingress created by the vcluster chart by default as this was conflicting with the new recommended spec.ingressClass
. To revert old behaviour, make sure to set the following values when deploying / upgrading your vcluster:
ingress:
annotations:
kubernetes.io/ingress.class: nginx
vcluster is now able to deploy helm charts defined in the chart values inside the virtual cluster on startup. For more information, please take a look at the vcluster docs
Published by FabianKramm about 2 years ago
We removed the deprecated kubernetes.io/ingress.class
annotation from the ingress created by the vcluster chart by default as this was conflicting with the new recommended spec.ingressClass
. To revert old behaviour, make sure to set the following values when deploying your vcluster:
ingress:
annotations:
kubernetes.io/ingress.class: nginx
vcluster is now able to deploy helm charts defined in the chart values inside the virtual cluster on startup. For more information, please take a look at the vcluster docs