diff --git a/faq/faq/index.html b/faq/faq/index.html index 830464ca..e9f88b78 100644 --- a/faq/faq/index.html +++ b/faq/faq/index.html @@ -671,7 +671,7 @@
--master
> 1 and no --datastore-x
option is set, the first master node (master-0) will be the initializing master node--cluster-init
flag appended--server https://<init-node>:6443
--output
flag), we use the default loading rules to get the default kubeconfig:--[update|merge]-default-kubeconfig
is set, we use the default loading rules to get the default kubeconfig:$HOME/.kube/config
)Get the kubeconfig file
-export KUBECONFIG="$(k3d get-kubeconfig --name='k3s-default')"
export KUBECONFIG="$(k3d get kubeconfig k3s-default)"
Create a nginx deployment
@@ -705,7 +705,7 @@ Therefore, we have to create the cluster in a way, that the internal port 80 (whk3d get kubeconfig mycluster
$HOME/.k3d/kubeconfig-mycluster.yaml
export KUBECONFIG=$(k3d get kubeconfig mycluster)
k3d create cluster mycluster --update-kubeconfig
--switch-context
to do so)k3d get kubeconfig mycluster
k3d get kubeconfig mycluster --merge-default-kubeconfig
--switch-context
to do so)Switching the current context
-None of the above options switch the current-context. +
None of the above options switch the current-context by default.
This is intended to be least intrusive, since the current-context has a global effect.
-You can switch the current-context directly with the get kubeconfig
command by adding the --switch
flag.
get kubeconfig
command by adding the --switch-context
flag.
k3d delete cluster mycluster
will always remove the details for mycluster
from the default kubeconfig.
k3d delete cluster mycluster
will always remove the details for mycluster
from the default kubeconfig.
+It will also delete the respective kubeconfig file in $HOME/.k3d/
if it exists.
k3d get kubeconfig
let’s you specify one or more clusters via arguments or all via --all
.
-All kubeconfigs will then be merged into a single file, which is either the default kubeconfig or the kubeconfig specified via --output FILE
.
-Note, that with multiple cluster specified, the --switch
flag will change the current context to the cluster which was last in the list.
--merge-default-kubeconfig
or --output
is specified.
+If none of those two flags was specified, a new file will be created per cluster and the merged path (e.g. $HOME/.k3d/kubeconfig-cluster1.yaml:$HOME/.k3d/cluster2.yaml
) will be returned.
+Note, that with multiple cluster specified, the --switch-context
flag will change the current context to the cluster which was last in the list.
@@ -665,7 +673,7 @@ Note, that with multiple cluster specified, the --switch
flag will
--cl
- Last update: May 16, 2020
+ Last update: May 16, 2020