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 visible (Hide)
Published by FabianKramm over 2 years ago
Plugins are a feature to extend the capabilities of vcluster. They allow you to add custom functionality, such as:
For more information, please take a look at the vcluster docs.
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
vcluster connect
in same shellvcluster now allows command execution with vcluster context in command vcluster connect
. For example:
# Retrieve vcluster namespaces
vcluster connect test -n test -- kubectl get ns
# New shell with vcluster kube context
vcluster connect test -n test -- bash
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
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
vcluster now suports syncing of pod disruption budgets between the host and virtual cluster, that can be enabled via a values.yaml
:
rbac:
role:
extended: true
syncer:
extraArgs:
- --sync=poddisruptionbudgets
and then used via:
vcluster create ... -f values.yaml
--insecure
for vcluster connect
to create a kube config with insecure-skip-tls-verify
vcluster create
can now use urls as value for -f
flagsvcluster get service-cidr
to print the current clusters service cidrvcluster create
vcluster connect
will now use a random port locally to avoid port conflicts if no --local-port
flag is specified.-s
for global flag --silent
vcluster-images.txt
which holds all the needed images by vcluster. In addition, we include two scripts to download and push the needed images automaticallyPublished by FabianKramm over 2 years ago
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
vcluster connect
in same shellvcluster now allows command execution with vcluster context in command vcluster connect
. For example:
# Retrieve vcluster namespaces
vcluster connect test -n test -- kubectl get ns
# New shell with vcluster kube context
vcluster connect test -n test -- bash
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
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
--insecure
for vcluster connect
to create a kube config with insecure-skip-tls-verify
vcluster get service-cidr
to print the current clusters service cidrvcluster create
vcluster connect
will now use a random port locally to avoid port conflicts if no --local-port
flag is specified.-s
for global flag --silent
vcluster-images.txt
which holds all the needed images by vcluster. In addition, we include two scripts to download and push the needed images automaticallyPublished by FabianKramm over 2 years ago
Published by FabianKramm over 2 years ago
Published by FabianKramm almost 3 years ago
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
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
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
--insecure
for vcluster connect
to create a kube config with insecure-skip-tls-verify
vcluster create
vcluster-images.txt
which holds all the needed images by vcluster. In addition, we include two scripts to download and push the needed images automaticallyPublished by FabianKramm almost 3 years ago
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
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
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
--insecure
for vcluster connect
to create a kube config with insecure-skip-tls-verify
vcluster create
vcluster-images.txt
which holds all the needed images by vcluster. In addition, we include two scripts to download and push the needed images automaticallyPublished by FabianKramm almost 3 years ago
Published by FabianKramm almost 3 years ago
Published by FabianKramm almost 3 years ago
Published by FabianKramm almost 3 years ago
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
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
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
--insecure
for vcluster connect
to create a kube config with insecure-skip-tls-verify
vcluster-images.txt
which holds all the needed images by vcluster. In addition, we include two scripts to download and push the needed images automaticallyPublished by FabianKramm almost 3 years ago
Published by FabianKramm almost 3 years ago
Published by FabianKramm almost 3 years ago
Published by FabianKramm almost 3 years ago
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
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
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
--insecure
for vcluster connect
to create a kube config with insecure-skip-tls-verify
vcluster-images.txt
which holds all the needed images by vcluster. In addition, we include two scripts to download and push the needed images automaticallyPublished by FabianKramm almost 3 years ago
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
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
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
--insecure
for vcluster connect
to create a kube config with insecure-skip-tls-verify
vcluster-images.txt
which holds all the needed images by vcluster. In addition, we include two scripts to download and push the needed images automaticallyPublished by FabianKramm almost 3 years ago
Published by FabianKramm almost 3 years ago
vcluster will now deploy coredns itself instead of depending on the k3s coredns deployment. This makes it possible to customize the coredns deployment (e.g. for rootless mode) and also support other kubernetes distributions besides k3s. However, this will break the current coredns deployment created by k3s.
This means that after you have upgraded vcluster from an v0.4.x
version, you need to delete the coredns deployment inside vcluster and then restart vcluster by deleting the vcluster pod to let it redeploy the correct coredns deployment:
# Delete coredns deployment inside vcluster
export KUBECONFIG=vcluster-kubeconfig.yaml
kubectl delete deployment coredns -n kube-system
# Restart vcluster by deleting its pod
export KUBECONFIG=host-kubeconfig.yaml
kubectl delete pod vcluster-pod-0 -n vcluster-namespace
vcluster now supports creating k0s and vanilla k8s virtual Kubernetes clusters instead of k3s. You can now specify the target virtual Kubernetes cluster distribution via the --distro
flag in vcluster create
. For vanilla k8s there is now also a high availability mode.
Examples:
# Create a virtual k3s Kubernetes cluster
vcluster create my-vcluster -n my-vcluster
# Create a virtual k0s Kubernetes cluster
vcluster create my-vcluster -n my-vcluster --distro k0s
# Create a virtual k8s Kubernetes cluster with kubernetes version v1.20
vcluster create my-vcluster -n my-vcluster --distro k8s --kubernetes-version v1.20
vcluster is now able to sync networkpolicies created within the vcluster to the host cluster. To enable networkpolicies, create a values.yaml
with:
rbac:
role:
extended: true
syncer:
extraArgs:
- --sync=networkpolicies
and then create the vcluster with:
vcluster create my-vcluster -n my-vcluster -f values.yaml
vcluster create
flags --release-values
and --k3s-image
. Use --extra-values
insteadvcluster create
flag --upgrade
from true
to false
. vcluster will not try to upgrade an existing vcluster by default anymore--kubernetes-version
for vcluster create
to override the kubernetes version used for creating the vcluster.defaultImageRegistry
that allows you to specify an image registry that should be prepended to all deployed system pods by vcluster--fake-kubelets
to --disable-fake-kubelets
that makes it easier to understand how to disable fake kubelets as they are enabled by default. --fake-kubelets
still exists and will be migrated automatically--sync
that defines enabled or disabled sync controllers similar to --controllers
of kube-controller-manager. Examples:
--sync=''
ingresses
: --sync=-ingresses
--sync=nodes
--sync=persistentvolumes
--sync=storageclasses,persistentvolumes
secrets,services,configmaps,endpoints,events,fake-persistentvolumes,ingresses,persistentvolumeclaims,pods,fake-nodes
secrets,services,configmaps,endpoints,events,fake-persistentvolumes,ingresses,nodes,persistentvolumeclaims,priorityclasses,pods,fake-nodes,persistentvolumes,storageclasses
--fake-kubelets
, --disable-sync-resources
, --enable-priority-classes
, --enable-storage-classes
, --fake-nodes
and --fake-persistent-volumes
--name
that specifies the vcluster name (replaces --suffix
)--suffix
, use --name
instead--service-name
now defaults to --name
if omitted--set-owner
now defaults to true
and vcluster does not fail if setting the owner is not possiblehealthCheckNodePort
was not correctly synced (#240)--service-namespace
as this would break vcluster if it's not the same value as current vcluster namespace--target-namespace
was provided (#214)--leader-elect
that defaults to false to avoid unnecessary leader electionPublished by FabianKramm almost 3 years ago
vcluster will now deploy coredns itself instead of depending on the k3s coredns deployment. This makes it possible to customize the coredns deployment (e.g. for rootless mode) and also support other kubernetes distributions besides k3s. However, this will break the current coredns deployment created by k3s.
This means that after you have upgraded vcluster from an v0.4.x
version, you need to delete the coredns deployment inside vcluster and then restart vcluster by deleting the vcluster pod to let it redeploy the correct coredns deployment:
# Delete coredns deployment inside vcluster
export KUBECONFIG=vcluster-kubeconfig.yaml
kubectl delete deployment coredns -n kube-system
# Restart vcluster by deleting its pod
export KUBECONFIG=host-kubeconfig.yaml
kubectl delete pod vcluster-pod-0 -n vcluster-namespace
vcluster now supports creating k0s and vanilla k8s virtual Kubernetes clusters instead of k3s. You can now specify the target virtual Kubernetes cluster distribution via the --distro
flag in vcluster create
. For vanilla k8s there is now also a high availability mode.
Examples:
# Create a virtual k3s Kubernetes cluster
vcluster create my-vcluster -n my-vcluster
# Create a virtual k0s Kubernetes cluster
vcluster create my-vcluster -n my-vcluster --distro k0s
# Create a virtual k8s Kubernetes cluster with kubernetes version v1.20
vcluster create my-vcluster -n my-vcluster --distro k8s --kubernetes-version v1.20
vcluster is now able to sync networkpolicies created within the vcluster to the host cluster. To enable networkpolicies, create a values.yaml
with:
rbac:
role:
extended: true
syncer:
extraArgs:
- --sync=networkpolicies
and then create the vcluster with:
vcluster create my-vcluster -n my-vcluster -f values.yaml
vcluster create
flags --release-values
and --k3s-image
. Use --extra-values
insteadvcluster create
flag --upgrade
from true
to false
. vcluster will not try to upgrade an existing vcluster by default anymore--kubernetes-version
for vcluster create
to override the kubernetes version used for creating the vcluster.defaultImageRegistry
that allows you to specify an image registry that should be prepended to all deployed system pods by vcluster--fake-kubelets
to --disable-fake-kubelets
that makes it easier to understand how to disable fake kubelets as they are enabled by default. --fake-kubelets
still exists and will be migrated automatically--sync
that defines enabled or disabled sync controllers similar to --controllers
of kube-controller-manager. Examples:
--sync=''
ingresses
: --sync=-ingresses
--sync=nodes
--sync=persistentvolumes
--sync=storageclasses,persistentvolumes
secrets,services,configmaps,endpoints,events,fake-persistentvolumes,ingresses,persistentvolumeclaims,pods,fake-nodes
secrets,services,configmaps,endpoints,events,fake-persistentvolumes,ingresses,nodes,persistentvolumeclaims,priorityclasses,pods,fake-nodes,persistentvolumes,storageclasses
--fake-kubelets
, --disable-sync-resources
, --enable-priority-classes
, --enable-storage-classes
, --fake-nodes
and --fake-persistent-volumes
--name
that specifies the vcluster name (replaces --suffix
)--suffix
, use --name
instead--service-name
now defaults to --name
if omitted--set-owner
now defaults to true
and vcluster does not fail if setting the owner is not possiblehealthCheckNodePort
was not correctly synced (#240)--service-namespace
as this would break vcluster if it's not the same value as current vcluster namespace--target-namespace
was provided (#214)--leader-elect
that defaults to false to avoid unnecessary leader electionPublished by FabianKramm almost 3 years ago
vcluster will now deploy coredns itself instead of depending on the k3s coredns deployment. This makes it possible to customize the coredns deployment (e.g. for rootless mode) and also support other kubernetes distributions besides k3s. However, this will break the current coredns deployment created by k3s.
This means that after you have upgraded vcluster from an v0.4.x
version, you need to delete the coredns deployment inside vcluster and then restart vcluster by deleting the vcluster pod to let it redeploy the correct coredns deployment:
# Delete coredns deployment inside vcluster
export KUBECONFIG=vcluster-kubeconfig.yaml
kubectl delete deployment coredns -n kube-system
# Restart vcluster by deleting its pod
export KUBECONFIG=host-kubeconfig.yaml
kubectl delete pod vcluster-pod-0 -n vcluster-namespace
vcluster now supports creating k0s and vanilla k8s virtual Kubernetes clusters instead of k3s. You can now specify the target virtual Kubernetes cluster distribution via the --distro
flag in vcluster create
. For vanilla k8s there is now also a high availability mode.
Examples:
# Create a virtual k3s Kubernetes cluster
vcluster create my-vcluster -n my-vcluster
# Create a virtual k0s Kubernetes cluster
vcluster create my-vcluster -n my-vcluster --distro k0s
# Create a virtual k8s Kubernetes cluster with kubernetes version v1.20
vcluster create my-vcluster -n my-vcluster --distro k8s --kubernetes-version v1.20
vcluster is now able to sync networkpolicies created within the vcluster to the host cluster. To enable networkpolicies, create a values.yaml
with:
rbac:
role:
extended: true
syncer:
extraArgs:
- --sync=networkpolicies
and then create the vcluster with:
vcluster create my-vcluster -n my-vcluster -f values.yaml
vcluster create
flags --release-values
and --k3s-image
. Use --extra-values
insteadvcluster create
flag --upgrade
from true
to false
. vcluster will not try to upgrade an existing vcluster by default anymore--kubernetes-version
for vcluster create
to override the kubernetes version used for creating the vcluster.defaultImageRegistry
that allows you to specify an image registry that should be prepended to all deployed system pods by vcluster--fake-kubelets
to --disable-fake-kubelets
that makes it easier to understand how to disable fake kubelets as they are enabled by default. --fake-kubelets
still exists and will be migrated automatically--sync
that defines enabled or disabled sync controllers similar to --controllers
of kube-controller-manager. Examples:
--sync=''
ingresses
: --sync=-ingresses
--sync=nodes
--sync=persistentvolumes
--sync=storageclasses,persistentvolumes
secrets,services,configmaps,endpoints,events,fake-persistentvolumes,ingresses,persistentvolumeclaims,pods,fake-nodes
secrets,services,configmaps,endpoints,events,fake-persistentvolumes,ingresses,nodes,persistentvolumeclaims,priorityclasses,pods,fake-nodes,persistentvolumes,storageclasses
--fake-kubelets
, --disable-sync-resources
, --enable-priority-classes
, --enable-storage-classes
, --fake-nodes
and --fake-persistent-volumes
--name
that specifies the vcluster name (replaces --suffix
)--suffix
, use --name
instead--service-name
now defaults to --name
if omitted--set-owner
now defaults to true
and vcluster does not fail if setting the owner is not possiblehealthCheckNodePort
was not correctly synced (#240)--service-namespace
as this would break vcluster if it's not the same value as current vcluster namespace--target-namespace
was provided (#214)--leader-elect
that defaults to false to avoid unnecessary leader electionPublished by FabianKramm almost 3 years ago
vcluster will now deploy coredns itself instead of depending on the k3s coredns deployment. This makes it possible to customize the coredns deployment (e.g. for rootless mode) and also support other kubernetes distributions besides k3s. However, this will break the current coredns deployment created by k3s.
This means that after you have upgraded vcluster from an v0.4.x
version, you need to delete the coredns deployment inside vcluster and then restart vcluster by deleting the vcluster pod to let it redeploy the correct coredns deployment:
# Delete coredns deployment inside vcluster
export KUBECONFIG=vcluster-kubeconfig.yaml
kubectl delete deployment coredns -n kube-system
# Restart vcluster by deleting its pod
export KUBECONFIG=host-kubeconfig.yaml
kubectl delete pod vcluster-pod-0 -n vcluster-namespace
vcluster now supports creating k0s and vanilla k8s virtual Kubernetes clusters instead of k3s. You can now specify the target virtual Kubernetes cluster distribution via the --distro
flag in vcluster create
. For vanilla k8s there is now also a high availability mode.
Examples:
# Create a virtual k3s Kubernetes cluster
vcluster create my-vcluster -n my-vcluster
# Create a virtual k0s Kubernetes cluster
vcluster create my-vcluster -n my-vcluster --distro k0s
# Create a virtual k8s Kubernetes cluster with kubernetes version v1.20
vcluster create my-vcluster -n my-vcluster --distro k8s --kubernetes-version v1.20
vcluster create
flags --release-values
and --k3s-image
. Use --extra-values
insteadvcluster create
flag --upgrade
from true
to false
. vcluster will not try to upgrade an existing vcluster by default anymore--kubernetes-version
for vcluster create
to override the kubernetes version used for creating the vcluster.defaultImageRegistry
that allows you to specify an image registry that should be prepended to all deployed system pods by vcluster--fake-kubelets
to --disable-fake-kubelets
that makes it easier to understand how to disable fake kubelets as they are enabled by default. --fake-kubelets
still exists and will be migrated automatically--sync
that defines enabled or disabled sync controllers similar to --controllers
of kube-controller-manager. Examples:
--sync=''
ingresses
: --sync=-ingresses
--sync=nodes
--sync=persistentvolumes
--sync=storageclasses,persistentvolumes
secrets,services,configmaps,endpoints,events,fake-persistentvolumes,ingresses,persistentvolumeclaims,pods,fake-nodes
secrets,services,configmaps,endpoints,events,fake-persistentvolumes,ingresses,nodes,persistentvolumeclaims,priorityclasses,pods,fake-nodes,persistentvolumes,storageclasses
--fake-kubelets
, --disable-sync-resources
, --enable-priority-classes
, --enable-storage-classes
, --fake-nodes
and --fake-persistent-volumes
--name
that specifies the vcluster name (replaces --suffix
)--suffix
, use --name
instead--service-name
now defaults to --name
if omitted--set-owner
now defaults to true
and vcluster does not fail if setting the owner is not possible--service-namespace
as this would break vcluster if it's not the same value as current vcluster namespace--target-namespace
was provided (#214)--leader-elect
that defaults to false to avoid unnecessary leader election