How to use NodePort with kind?

Patryk picture Patryk · Jun 17, 2020 · Viewed 8.5k times · Source

I'm trying to use NodePort with kind but somehow it doesn't want to work.

I've successfully deployed the following cluster:

apiVersion: kind.x-k8s.io/v1alpha4
kind: Cluster
nodes:
- role: control-plane
  extraPortMappings:
  - containerPort: 80
    hostPort: 30000
    listenAddress: "0.0.0.0" # Optional, defaults to "0.0.0.0"
    protocol: tcp # Optional, defaults to tcp
- role: worker

and then a very simple deployment:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: hostname-deployment
  labels:
    app: hostname
spec:
  replicas: 2
  selector:
    matchLabels:
      app: hostname
  template:
    metadata:
      labels:
        app: hostname
    spec:
      containers:
      - name: hostname
        image: hostname:0.1
        ports:
        - containerPort: 80

and a service:

apiVersion: v1
kind: Service
metadata:
  name: hostname-service
spec:
  type: NodePort
  selector:
    app: hostname
  ports:
    - protocol: TCP
      port: 80
      targetPort: 80
      nodePort: 30000

and I can connect to the service via e.g.

(in one terminal)
k port-forward service/hostname-service 8080:80
Forwarding from 127.0.0.1:8080 -> 80

(another one)
curl localhost:8080
hostname: hostname-deployment-75c9fd6584-ddc59 at Wed, 17 Jun 2020 15:38:33 UTC

But I cannot connect to the service via the exposed NodePort

curl -v localhost:30000
* Rebuilt URL to: localhost:30000/
*   Trying 127.0.0.1...
* TCP_NODELAY set
* Connected to localhost (127.0.0.1) port 30000 (#0)
> GET / HTTP/1.1
> Host: localhost:30000
> User-Agent: curl/7.58.0
> Accept: */*
>
* Recv failure: Connection reset by peer
* stopped the pause stream!
* Closing connection 0
curl: (56) Recv failure: Connection reset by peer

kubectl get all output:

NAME                                       READY   STATUS    RESTARTS   AGE
pod/hostname-deployment-75c9fd6584-ddc59   1/1     Running   0          34m
pod/hostname-deployment-75c9fd6584-tg8db   1/1     Running   0          34m

NAME                       TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)        AGE
service/hostname-service   NodePort    10.107.104.231   <none>        80:30000/TCP   34m
service/kubernetes         ClusterIP   10.96.0.1        <none>        443/TCP        35m

NAME                                  READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/hostname-deployment   2/2     2            2           34m

NAME                                             DESIRED   CURRENT   READY   AGE
replicaset.apps/hostname-deployment-75c9fd6584   2         2         2       34m

Answer

Arghya Sadhu picture Arghya Sadhu · Jun 17, 2020

Kind cluster configuration needs to be like below

apiVersion: kind.x-k8s.io/v1alpha4
kind: Cluster
nodes:
- role: control-plane
  extraPortMappings:
  - containerPort: 30000
    hostPort: 30000
    listenAddress: "0.0.0.0" # Optional, defaults to "0.0.0.0"
    protocol: tcp # Optional, defaults to tcp
- role: worker

This file is then passed to your creation command as kind create cluster --config=config.yaml (according to docs).