k3d is a lightweight wrapper to run k3s (Rancher Lab’s minimal Kubernetes distribution) in docker.
k3d makes it very easy to create single- and multi-node k3s clusters in docker, e.g. for local development on Kubernetes.
In this example, we will deploy a simple nginx webserver deployment and make it accessible via ingress. Therefore, we have to create the cluster in a way, that the internal port 80 (where the traefik ingress controller is listening on) is exposed on the host system.
Create a cluster, mapping the ingress port 80 to localhost:8081
--api-port 6550 is not required for the example to work. It’s used to have k3s‘s API-Server listening on port 6550 with that port mapped to the host system.
the port-mapping construct8081:80@loadbalancermeans
map port 8081 from the host to port 80 on the container which matches the nodefilter loadbalancer
theloadbalancernodefilter matches only theserverlb that’s deployed in front of a cluster’s server nodes
all ports exposed on the serverlb will be proxied to the same ports on all server nodes in the cluster
Note: Kubernetes’ default NodePort range is 30000-32767
Note: You may as well expose the whole NodePort range from the very beginning, e.g. via k3d cluster create mycluster --agents 3 -p "30000-32767:30000-32767@server[0]" (See this video from @portainer)
… (Steps 2 and 3 like above) …
Create a NodePort service for it with kubectl apply -f