We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A new ~/.kube/config is recreated upon cluster creation.
Just created a cluster.
Contents should be added into existing ~/.kube/config whether it's an ordinary file or symlink.
# before ❯ ls -l drwxr-x--- 4 dennybaa dennybaa 4096 Sep 7 15:59 cache lrwxrwxrwx 1 dennybaa dennybaa 18 Oct 8 20:36 config -> default.kubeconfig # after ❯ ls -l drwxr-x--- 4 dennybaa dennybaa 4096 Sep 7 15:59 cache -rw------- 1 dennybaa dennybaa 5883 Oct 8 20:38 config -rw------- 1 dennybaa dennybaa 2990 Oct 8 20:35 default.kubeconfig
arch: amd64 cgroupdriver: systemd cgroupversion: "2" endpoint: /run/user/1000/podman/podman.sock filesystem: extfs name: docker os: pop ostype: linux version: 4.6.2
k3d
k3d version v5.6.0 k3s version v1.27.4-k3s1 (default)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
A new ~/.kube/config is recreated upon cluster creation.
What did you do
Just created a cluster.
What did you expect to happen
Contents should be added into existing ~/.kube/config whether it's an ordinary file or symlink.
Screenshots or terminal output
Which OS & Architecture
Which version of
k3d
The text was updated successfully, but these errors were encountered: