!! BREAKING CHANGES !!
vcluster createnow automatically does a connect by default. Can be disabled viavcluster create --connect=falsevcluster connectnow by default switches the current kube context to the vcluster context. Can be disabled viavcluster connect --update-current=falsevcluster deletenow by default deletes the namespace of the vcluster if it was created by vcluster before. Can be disabled viavcluster delete --auto-delete-namespace=false
Greatly improved vcluster cli experience
In this release we focused on improving the CLI experience for vcluster. On most local kubernetes distributions (minikube, docker-desktop, k3d, kind) you are now able to start vcluster without port-forwarding which makes it a lot easier to get started and use vcluster for local k8s development. It's also great news if you consider using vcluster in your CI/CD pipelines as you can now use KIND and vcluster together without having to run vcluster connect in the background anymore.
So the current vcluster create && vcluster connect flow in a separate terminal simplifies to:
# Start and connect a new vcluster in a single command for local Kubernetes distros
vcluster create my-vcluster
# Then immediately access the vcluster with regular kubectl commands
kubectl get ns
# Disconnect or delete the vcluster when you are done to switch back
# to the host context
vcluster disconnect
Changes
- cli: New flag
--kube-config-context-nameforvcluster connect