change the kubelet’s eviction thresholds upon cluster creation:
k3d cluster create \
- --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%'
+ --k3s-arg '--kubelet-arg=eviction-hard=imagefs.available<1%,nodefs.available<1%@agent:*' \
+ --k3s-arg '--kubelet-arg=eviction-minimum-reclaim=imagefs.available=1%,nodefs.available=1%@agent:*'
k3d cluster create --k3s-server-arg '--kube-apiserver-arg=feature-gates=EphemeralContainers=true'k3d cluster create --k3s-arg '--kube-apiserver-arg=feature-gates=EphemeralContainers=true@server:*'--) and where not.--kube-apiserver-arg) has the dashesfeature-gates doesn’t have them (k3s adds them internally)Second example:
k3d cluster create k3d-one \
- --k3s-server-arg --cluster-cidr="10.118.0.0/17" \
- --k3s-server-arg --service-cidr="10.118.128.0/17" \
- --k3s-server-arg --disable=servicelb \
- --k3s-server-arg --disable=traefik \
+ --k3s-arg "--cluster-cidr=10.118.0.0/17@server:*" \
+ --k3s-arg "--service-cidr=10.118.128.0/17@server:*" \
+ --k3s-arg "--disable=servicelb@server:*" \
+ --k3s-arg "--disable=traefik@server:*" \
--verbose
HTTP_PROXY environment variables t
Workaround: as a workaround, we can tell kube-proxy to not even try to set this value:
k3d cluster create \
- --k3s-server-arg "--kube-proxy-arg=conntrack-max-per-core=0" \
- --k3s-agent-arg "--kube-proxy-arg=conntrack-max-per-core=0" \
+ --k3s-arg "--kube-proxy-arg=conntrack-max-per-core=0@server:*" \
+ --k3s-arg "--kube-proxy-arg=conntrack-max-per-core=0@agent:*" \
--image rancher/k3s:v1.20.6-k3s
On the k3s cluster creation :
--flannel-backend=none. For this, on k3d you need to forward this flag to k3s with the option --k3s-server-arg.--flannel-backend=none. For this, on k3d you need to forward this flag to k3s with the option --k3s-arg.--volume) the calico descriptor in the auto deploy manifest directory of k3s /var/lib/rancher/k3s/server/manifests/So the command of the cluster creation is (when you are at root of the k3d repository)
k3d cluster create "${clustername}" \
- --k3s-server-arg '--flannel-backend=none' \
+ --k3s-arg '--flannel-backend=none@server:*' \
--volume "$(pwd)/docs/usage/guides/calico.yaml:/var/lib/rancher/k3s/server/manifests/calico.yaml"
In this example :
@@ -1098,7 +1098,7 @@ coredns-8655855d6-cxtnr 1/1 Runnin/etc/ssl/certs/my-company-root.pem
Create a customized k3d-managed registry¶
k3d registry create myregistry.localhost --port 12345 creates a new registry called k3d-myregistry.localhost (could be used with automatic resolution of *.localhost, see next section - also, note the k3d- prefix that k3d adds to all resources it creates)k3d cluster create newcluster --registry-use k3d-myregistry.localhost:12345 (make sure you use the k3d- prefix here) creates a new cluster set up to us that registryk3d cluster create newcluster --registry-use k3d-myregistry.localhost:12345 (make sure you use the k3d- prefix here) creates a new cluster set up to use that registry- continue with step 3 and 4 from the last section for testing
@@ -1336,7 +1336,7 @@ docker push k3d-registry.localhost:5000/nginx:latest
- Last update: September 17, 2021
+ Last update: October 11, 2021