mirror of https://github.com/k3d-io/k3d
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.
2.7 KiB
2.7 KiB
FAQ / Nice to know
Issues with BTRFS
- As @jaredallard pointed out, people running
k3don a system with btrfs, may need to mount/dev/mapperinto the nodes for the setup to work.- This will do:
k3d create cluster CLUSTER_NAME -v /dev/mapper:/dev/mapper
- This will do:
Issues with ZFS
-
k3s currently has no support for ZFS and thus, creating multi-master setups (e.g.
k3d create cluster multimaster --masters 3) fails, because the initializing master node (server flag--cluster-init) errors out with the following log:starting kubernetes: preparing server: start cluster and https: raft_init(): io: create I/O capabilities probe file: posix_allocate: operation not supported on socket- This issue can be worked around by providing docker with a different filesystem (that's also better for docker-in-docker stuff).
- A possible solution can be found here: https://github.com/rancher/k3s/issues/1688#issuecomment-619570374
Pods evicted due to lack of disk space
- Pods go to evicted state after doing X
- Related issues: #133 - Pods evicted due to
NodeHasDiskPressure(collection of #119 and #130) - Background: somehow docker runs out of space for the k3d node containers, which triggers a hard eviction in the kubelet
- Possible fix/workaround by @zer0def:
- use a docker storage driver which cleans up properly (e.g. overlay2)
- clean up or expand docker root filesystem
- change the kubelet's eviction thresholds upon cluster creation:
k3d create cluster --k3s-agent-arg '--kubelet-arg=eviction-hard=imagefs.available<1%,nodefs.available<1%' --k3s-agent-arg '--kubelet-arg=eviction-minimum-reclaim=imagefs.available=1%,nodefs.available=1%'
- Related issues: #133 - Pods evicted due to
Restarting a multi-master cluster or the initializing master node fails
- What you do: You create a cluster with more than one master node and later, you either stop
master-0or stop/start the whole cluster - What fails: After the restart, you cannot connect to the cluster anymore and
kubectlwill give you a lot of errors - What causes this issue: it's a known issue with dqlite in
k3swhich doesn't allow the initializing master node to go down - What's the solution: Hopefully, this will be solved by the planned replacement of dqlite with embedded etcd in k3s
- Related issues: #262