Overall, we will look at everything you need to develop and test apps on Kubernetes in your local workstation using kind.<\/p>\n
What is Kind Cluster?<\/h2>\n
Kind<\/a> is a tool that is used to create a portable and lightweight Kubernetes cluster<\/a>. It is the best choice for testing general use cases because it is easy to deploy and delete.<\/p>\n Kind runs on Docker<\/a>. Meaning, when you create a Kind Cluster, Docker containers<\/a> are created and act as cluster nodes.<\/p>\n In the backend, Kind used Kubeadm<\/a> to bootstrap the cluster.<\/p>\n Also, the Kind cluster will not get deleted even after system restarts, and if you are using Docker Desktop, you can pause the containers using Docker Desktop dashboard.<\/p>\n Before going further, make sure you have the following prerequisites.<\/p>\n Follow the steps below to set up a Kind cluster in your system.<\/p>\n Before creating the cluster, you need to install Kind on your system.<\/p>\n Run the following commands based on your OS.<\/p>\n For Linux:<\/p>\n For Mac:<\/p>\n For Windows PowerShell:<\/p>\n To create a Kind cluster, you need a YAML config file. Create a YAML file This config file will create a three node cluster, 1 control plane, and two worker nodes.<\/p>\n Under the We are using ports Run the following command to create a Kind cluster with the configurations in the YAML file.<\/p>\n Once it is created, you can see the following output.<\/p>\n The cluster context will be added to kubeconfig file<\/a> automatically, run the following to verify if kubectl can access the cluster.<\/p>\n You can see the nodes of the Kind cluster.<\/p>\n For testing the cluster, we are going to do the following:<\/p>\n In this section, you will deploy an Nginx application in the Kind cluster and expose it using NodePort.<\/p>\n To deploy the application, create a YAML file This file will create a Nginx deployment. Run the following command to deploy it.<\/p>\n Then, run the following command to verify if the pod is created.<\/p>\n Before exposing using NodePort, you should know that we can only use the NodePorts that are specified during cluster creation.<\/p>\n According to our config file, the NodePorts we specified are We are going to expose the application using NodePort Run the following command to create it.<\/p>\n Then run the following command to check if the service is created.<\/p>\n You will get the following output.<\/p>\n Now, use the URL To expose the application using LoadBalancer on a Kind cluster, you can either use MetalLB or the cloud provider<\/a> Kind.<\/p>\n For this setup, we will be using MetalLB is a LoadBalancer for Kubernetes clusters that are running on a local system.<\/p>\n To install MetalLB in the cluster, run the following command.<\/p>\n Once it’s installed, run the following command to get the Kind clusters CIDR range.<\/p>\n You will get both IPv4 and IPv6 subnets as showb below.<\/p>\n From that use the IPv4 range Now, create an IP pool for MetalLB with a range from the Kind clusters CIDR, the external IP assigned to the service type LoadBalancer will be taken from this pool. <\/p>\n Create a YAML file On Linux\/macOS execute On Windows run Run the following command to create the IP pool.<\/p>\n We are going to expose the same Nginx application using a service type Create a YAML file We must specify the NodePort we specified during cluster creation because, if it assigns a random nodeport, we cannot access it outside the cluster.<\/p>\n Run the following command to create the service.<\/p>\n Now, run the following command to check the service, if an external IP is assigned.<\/p>\n You will get the following output.<\/p>\n If the external IP is assigned, try accessing it on the browser using the URL To expose a service in a Kind cluster using Ingress<\/a>, first you should make sure that you have created the cluster with ports 80 and 443 inside the extraPortMappings.<\/p>\n Install the Ingress controller<\/a> by running the following commands.<\/p>\n Now, create a service type ClusterIP for the same Nginx application to map ingress to that service.<\/p>\n Create a YAML file Then, run the following command to create the service.<\/p>\n Now, create an Ingress object for the service.<\/p>\n Create a YAML file Then, run the following command to create the Ingress object.<\/p>\n Run the following command to check if the ingress is created.<\/p>\n You will get the following output.<\/p>\n To access it on the web, you need the Ingress controller IP. Run the following command to get the IP assigned to the Ingress controller by MetalLB.<\/p>\n You can see the IP as shown below.<\/p>\n Use the IP on the browser, and you will get the following output.<\/p>\n Unlike Linux, in Mac and Windows, the Docker containers runs in a Linux VM by the Docker desktop. Because of this, the container is not exposed to the host system, and you cannot access it using IP<\/a>.<\/p>\n So, we are going to create a temporary Docker container and use curl to check the exposed application.<\/p>\n You will get the following output.<\/p>\n Now, let’s see how we can use Persistent Volume in Kind cluster.<\/p>\n For PV, the Kind cluster uses the local-path-provisioner by default.<\/p>\n Let’s deploy a MySQL StatefulSet with PVC.<\/p>\n Create a YAML file Run the following command to deploy the StatefulSet.<\/p>\n Then, run the following command to check if the StatefulSet pod and volume are created.<\/p>\n You will get the following output.<\/p>\n To enable feature gates in the Kind cluster, you need to add the featureGates paramter with the required featureGates.<\/p>\n For example, in the following cluster config, I have enabled the This will be helpful for you to test new features of Kubernetes.<\/p>\nSetup Prerequisites<\/h2>\n
\n
Step 1: Install Kind<\/h2>\n
[ $(uname -m) = x86_64 ] && curl -Lo .\/kind https:\/\/kind.sigs.k8s.io\/dl\/v0.29.0\/kind-linux-amd64\n\n[ $(uname -m) = aarch64 ] && curl -Lo .\/kind https:\/\/kind.sigs.k8s.io\/dl\/v0.29.0\/kind-linux-arm64\n\nchmod +x .\/kind\n\nsudo mv .\/kind \/usr\/local\/bin\/kind<\/code><\/pre>\nbrew install kind<\/code><\/pre>\ncurl.exe -Lo kind-windows-amd64.exe https:\/\/kind.sigs.k8s.io\/dl\/v0.29.0\/kind-windows-amd64\n\nMove-Item .\\kind-windows-amd64.exe c:\\some-dir-in-your-PATH\\kind.exe<\/code><\/pre>\nStep 2: Create Kind Cluster<\/h2>\n
kind-cluster.yaml<\/code> and copy the following content.<\/p>\nkind: Cluster\napiVersion: kind.x-k8s.io\/v1alpha4\nname: multi-node-cluster\nnodes:\n - role: control-plane\n image: kindest\/node:v1.33.0\n extraPortMappings:\n - containerPort: 30000\n hostPort: 30000\n protocol: TCP\n - containerPort: 31000\n hostPort: 31000\n protocol: TCP\n - containerPort: 32000\n hostPort: 32000\n protocol: TCP\n - containerPort: 80\n hostPort: 80\n protocol: TCP\n - containerPort: 443\n hostPort: 443\n protocol: TCP\n - role: worker\n image: kindest\/node:v1.33.0\n - role: worker\n image: kindest\/node:v1.33.0<\/code><\/pre>\nnodes<\/code> block, you can see the following:<\/p>\n\n
NodePorts<\/code><\/strong>.<\/li>\n<\/ul>\n80<\/code> and 443<\/code> inside the extraPortMappings<\/code><\/strong> for Ingress.<\/p>\nkind create cluster --config kind-cluster.yaml<\/code><\/pre>\n![\"\"](\"https:\/\/storage.ghost.io\/c\/5f\/2f\/5f2f4d20-2abf-4534-8d40-7aa233aedd43\/content\/images\/2025\/08\/image-64.png\")
<\/figure>\nkubectl get no<\/code><\/pre>\n![\"\"](\"https:\/\/storage.ghost.io\/c\/5f\/2f\/5f2f4d20-2abf-4534-8d40-7aa233aedd43\/content\/images\/2025\/08\/image-65.png\")
<\/figure>\nTesting Kind Cluster<\/h2>\n
\n
Deploy a simple Nginx on the Kind Cluster<\/h3>\n
deploy.yaml<\/code> and copy the following content.<\/p>\napiVersion: apps\/v1\nkind: Deployment\nmetadata:\n name: nginx-deployment\nspec:\n replicas: 1\n selector:\n matchLabels:\n app: nginx-demo\n template:\n metadata:\n labels:\n app: nginx-demo\n spec:\n containers:\n - name: nginx\n image: nginx:latest\n ports:\n - containerPort: 80\n<\/code><\/pre>\nkubectl apply -f deploy.yaml<\/code><\/pre>\nkubectl get po<\/code><\/pre>\nExpose the Application using NodePort<\/h3>\n
30000, 31000, and 32000<\/code>.<\/p>\n32000<\/code> , for that, create a YAML file nodeport-svc.yaml<\/code> and copy the following content.<\/p>\napiVersion: v1\nkind: Service\nmetadata:\n name: nginx-nodeport\nspec:\n type: NodePort\n selector:\n app: nginx-demo\n ports:\n - name: http\n port: 80\n targetPort: 80\n nodePort: 32000\n<\/code><\/pre>\nkubectl apply -f nodeport-svc.yaml<\/code><\/pre>\nkubectl get svc<\/code><\/pre>\n![\"verifying](\"https:\/\/storage.ghost.io\/c\/5f\/2f\/5f2f4d20-2abf-4534-8d40-7aa233aedd43\/content\/images\/2025\/08\/image-69.png\")
<\/figure>\nlocalhost:32000<\/code> to get the Nginx webpage in the browser.<\/p>\n![\"accessing](\"https:\/\/storage.ghost.io\/c\/5f\/2f\/5f2f4d20-2abf-4534-8d40-7aa233aedd43\/content\/images\/2025\/09\/image-69.png\")
<\/figure>\nExpose applications in Kind Cluster using LoadBalancer<\/h2>\n
MetalLB<\/code>. It will act as a software load balancer and assigns a IP address form your local IP pool assigned in your system. <\/p>\nInstall and Configure MetalLB<\/h3>\n
kubectl apply -f https:\/\/raw.githubusercontent.com\/metallb\/metallb\/v0.15.2\/config\/manifests\/metallb-native.yaml<\/code><\/pre>\ndocker network inspect kind | jq -r '.[0].IPAM.Config[].Subnet'<\/code><\/pre>\nfc00:f853:ccd:e793::\/64\n172.18.0.0\/16<\/code><\/pre>\n172.18.0.0\/16<\/code>.<\/p>\nmetallb-pool.yaml<\/code> and copy the following content.<\/p>\n172.18.0.100 - 172.18.0.200<\/code> if your CIDR range is other than 172.18.0.0\/16<\/code><\/p>\nip addr show<\/code> and look for something like en0 entries. <\/p>\nipconfig<\/code> and check IPv4 Address + Subnet Mask<\/div>\n<\/div>\napiVersion: metallb.io\/v1beta1\nkind: IPAddressPool\nmetadata:\n name: lb-pool\n namespace: metallb-system\nspec:\n addresses:\n - 172.18.0.100 - 172.18.0.200\n---\napiVersion: metallb.io\/v1beta1\nkind: L2Advertisement\nmetadata:\n name: l2\n namespace: metallb-system\nspec:\n ipAddressPools:\n - lb-pool\n<\/code><\/pre>\nkubectl apply -f metallb-pool.yaml\n<\/code><\/pre>\nExpose Application using LoadBalancer<\/h3>\n
LoadBalancer<\/code>.<\/p>\nlb-svc.yaml<\/code> and copy the following content.<\/p>\napiVersion: v1\nkind: Service\nmetadata:\n name: nginx-lb\nspec:\n type: LoadBalancer\n selector:\n app: nginx-demo\n ports:\n - name: http\n port: 80\n targetPort: 80\n nodePort: 31000<\/code><\/pre>\nkubectl apply -f lb-svc.yaml<\/code><\/pre>\nkubectl get svc<\/code><\/pre>\n![\"verifying](\"https:\/\/storage.ghost.io\/c\/5f\/2f\/5f2f4d20-2abf-4534-8d40-7aa233aedd43\/content\/images\/2025\/08\/image-71.png\")
<\/figure>\nlocalhost:31000<\/code>.<\/p>\n![\"accessing](\"https:\/\/storage.ghost.io\/c\/5f\/2f\/5f2f4d20-2abf-4534-8d40-7aa233aedd43\/content\/images\/2025\/09\/image-70.png\")
<\/figure>\nExpose Services in Kind Cluster using Ingress<\/h2>\n
kubectl apply -f https:\/\/kind.sigs.k8s.io\/examples\/ingress\/deploy-ingress-nginx.yaml\n\nkubectl wait --namespace ingress-nginx \\\n --for=condition=ready pod \\\n --selector=app.kubernetes.io\/component=controller \\\n --timeout=90s<\/code><\/pre>\nservice.yaml<\/code> and copy the following content.<\/p>\napiVersion: v1\nkind: Service\nmetadata:\n name: nginx-svc\nspec:\n type: ClusterIP\n selector:\n app: nginx-demo\n ports:\n - name: http\n port: 80\n targetPort: 80<\/code><\/pre>\nkubectl apply -f service.yaml<\/code><\/pre>\ningress.yaml<\/code> and copy the following content.<\/p>\napiVersion: networking.k8s.io\/v1\nkind: Ingress\nmetadata:\n name: nginx-ingress\nspec:\n ingressClassName: nginx\n rules:\n - http:\n paths:\n - path: \/\n pathType: Prefix\n backend:\n service:\n name: nginx-svc\n port:\n number: 80<\/code><\/pre>\nkubectl apply -f ingress.yaml<\/code><\/pre>\nkubectl get ingress<\/code><\/pre>\n![\"verifying](\"https:\/\/storage.ghost.io\/c\/5f\/2f\/5f2f4d20-2abf-4534-8d40-7aa233aedd43\/content\/images\/2025\/08\/image-80.png\")
<\/figure>\nkubectl get svc -n ingress-nginx<\/code><\/pre>\n![\"getting](\"https:\/\/storage.ghost.io\/c\/5f\/2f\/5f2f4d20-2abf-4534-8d40-7aa233aedd43\/content\/images\/2025\/08\/image-81.png\")
<\/figure>\n![\"accessing](\"https:\/\/storage.ghost.io\/c\/5f\/2f\/5f2f4d20-2abf-4534-8d40-7aa233aedd43\/content\/images\/2025\/09\/image-71.png\")
<\/figure>\ndocker run --rm --network kind curlimages\/curl curl -i http:\/\/172.18.0.101<\/code><\/pre>\n![\"sending](\"https:\/\/storage.ghost.io\/c\/5f\/2f\/5f2f4d20-2abf-4534-8d40-7aa233aedd43\/content\/images\/2025\/08\/image-83.png\")
<\/figure>\nUsing Persistent Volume in Kind<\/h2>\n
mysql.yaml<\/code> and copy the following content.<\/p>\napiVersion: apps\/v1\nkind: StatefulSet\nmetadata:\n name: mysql\nspec:\n serviceName: \"mysql\"\n replicas: 1\n selector:\n matchLabels:\n app: mysql\n template:\n metadata:\n labels:\n app: mysql\n spec:\n containers:\n - name: mysql\n image: mysql:latest\n env:\n - name: MYSQL_ROOT_PASSWORD\n value: rootpass\n ports:\n - containerPort: 3306\n volumeMounts:\n - name: mysql-data\n mountPath: \/var\/lib\/mysql\n volumeClaimTemplates:\n - metadata:\n name: mysql-data\n spec:\n accessModes: [\"ReadWriteOnce\"]\n resources:\n requests:\n storage: 2Gi<\/code><\/pre>\nkubectl apply -f mysql.yaml<\/code><\/pre>\nkubectl get po, pvc, pv<\/code><\/pre>\n![\"checking](\"https:\/\/storage.ghost.io\/c\/5f\/2f\/5f2f4d20-2abf-4534-8d40-7aa233aedd43\/content\/images\/2025\/09\/image-68.png\")
<\/figure>\nEnabling Feature Gates in Kind<\/h2>\n
ImageVolume<\/code><\/strong> feature gate.<\/p>\nkind: Cluster\napiVersion: kind.x-k8s.io\/v1alpha4\nname: multi-node-cluster\nfeatureGates:\n ImageVolume: true<\/code><\/pre>\n