gregandev
/
k3d
mirror of https://github.com/k3d-io/k3d
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
Little helper to run CNCF's k3s in Docker
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
938 Commits
25 Branches
165 Tags
70 MiB
 
 
 
 
Tag: Branch: Tree: 296f24c9b7
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '296f24c9b7'
${ noResults }
k3d/docs/internals/defaults.md

1.0 KiB
Raw Blame History

Defaults

Multiple server nodes

  • by default, when --server > 1 and no --datastore-x option is set, the first server node (server-0) will be the initializing server node
    • the initializing server node will have the --cluster-init flag appended
    • all other server nodes will refer to the initializing server node via --server https://<init-node>:6443

API-Ports

  • by default, we expose the API-Port (6443) by forwarding traffic from the default server loadbalancer (nginx container) to the server node(s)
  • port 6443 of the loadbalancer is then mapped to a specific (--api-port flag) or a random (default) port on the host system

Kubeconfig

  • if --kubeconfig-update-default is set, we use the default loading rules to get the default kubeconfig:
    • First: kubeconfig specified via the KUBECONFIG environment variable (error out if multiple are specified)
    • Second: default kubeconfig in home directory (e.g. $HOME/.kube/config)

Networking