Why my Nodeport service change its port number?

Question

I am trying to install the velero for k8s. During the installation when try to install mini.io I changes its service type from cluster IP to Node Port. My Pods run successfully and also I can see the node Port services is up and running.

master-k8s@masterk8s-virtual-machine:~/velero-v1.9.5-linux-amd64$ kubectl get pods -n velero -owide              NAME                     READY   STATUS    RESTARTS   AGE   IP             NODE                       NOMINATED NODE   READINESS GATES
minio-8649b94fb5-vk7gv   1/1     Running   0          16m   10.244.1.102   node1k8s-virtual-machine   <none>           <none>
master-k8s@masterk8s-virtual-machine:~/velero-v1.9.5-linux-amd64$ kubectl get svc -n velero                      NAME    TYPE       CLUSTER-IP      EXTERNAL-IP   PORT(S)          AGE
minio   NodePort   10.111.72.207   <none>        9000:31481/TCP   53m

When I try to access my services port number changes from 31481 to 45717 by it self. Every time when I correct port number and hit enter it changes back to new port and I am not able to access my application.

These are my codes from mini.io service file.

apiVersion: v1
kind: Service
metadata:
  namespace: velero
  name: minio
  labels:
    component: minio
spec:
  type: NodePort
  ports:
    - port: 9000
      targetPort: 9000
      protocol: TCP
  selector:
    component: minio

What I have done so far?

I look for the log and everything show successful No error. I also try it with Load balancer service. With Load balancer port not not changes but I am not able to access the application. Noting found on google about this issue. I also check all the namespaces pods and services to check if these Port numbers are being used. No services use these ports.

What Do I want? Can you please help me to find out what cause my application to change its port. Where is the issue and how to fix it.? How can I access application dashbord?

Update Question

This is the full codes file. It may help to find my mistake.

apiVersion: v1
kind: Namespace
metadata:
  name: velero

---
apiVersion: apps/v1
kind: Deployment
metadata:
  namespace: velero
  name: minio
  labels:
    component: minio
spec:
  strategy:
    type: Recreate
  selector:
    matchLabels:
      component: minio
  template:
    metadata:
      labels:
        component: minio
    spec:
      volumes:
      - name: storage
        emptyDir: {}
      - name: config
        emptyDir: {}
      containers:
      - name: minio
        image: minio/minio:latest
        imagePullPolicy: IfNotPresent
        args:
        - server
        - /storage
        - --config-dir=/config
        env:
        - name: MINIO_ACCESS_KEY
          value: "minio"
        - name: MINIO_SECRET_KEY
          value: "minio123"
        ports:
        - containerPort: 9002
        volumeMounts:
        - name: storage
          mountPath: "/storage"
        - name: config
          mountPath: "/config"

---
apiVersion: v1
kind: Service
metadata:
  namespace: velero
  name: minio
  labels:
    component: minio
spec:
  # ClusterIP is recommended for production environments.
  # Change to NodePort if needed per documentation,
  # but only if you run Minio in a test/trial environment, for example with Minikube.
  type: NodePort
  ports:
    - port: 9002
      nodePort: 31482
      targetPort: 9002
      protocol: TCP
  selector:
    component: minio

---
apiVersion: batch/v1
kind: Job
metadata:
  namespace: velero
  name: minio-setup
  labels:
    component: minio
spec:
  template:
    metadata:
      name: minio-setup
    spec:
      restartPolicy: OnFailure
      volumes:
      - name: config
        emptyDir: {}
      containers:
      - name: mc
        image: minio/mc:latest
        imagePullPolicy: IfNotPresent
        command:
        - /bin/sh
        - -c
        - "mc --config-dir=/config config host add velero http://minio:9000 minio minio123 && mc --config-dir=/config mb -p velero/velero"
        volumeMounts:
        - name: config
          mountPath: "/config"

Edit2 Logs Of Pod

WARNING: MINIO_ACCESS_KEY and MINIO_SECRET_KEY are deprecated.
         Please use MINIO_ROOT_USER and MINIO_ROOT_PASSWORD
Formatting 1st pool, 1 set(s), 1 drives per set.
WARNING: Host local has more than 0 drives of set. A host failure will result in data becoming unavailable.
MinIO Object Storage Server
Copyright: 2015-2023 MinIO, Inc.
License: GNU AGPLv3 <https://www.gnu.org/licenses/agpl-3.0.html>
Version: RELEASE.2023-01-25T00-19-54Z (go1.19.4 linux/amd64)

Status:         1 Online, 0 Offline.
API: http://10.244.1.108:9000  http://127.0.0.1:9000
Console: http://10.244.1.108:33045 http://127.0.0.1:33045

Documentation: https://min.io/docs/minio/linux/index.html
Warning: The standard parity is set to 0. This can lead to data loss.

Edit 3 Logs of Pod

master-k8s@masterk8s-virtual-machine:~/velero-1.9.5$ kubectl logs minio-8649b94fb5-qvzfh -n velero
WARNING: MINIO_ACCESS_KEY and MINIO_SECRET_KEY are deprecated.
         Please use MINIO_ROOT_USER and MINIO_ROOT_PASSWORD
Formatting 1st pool, 1 set(s), 1 drives per set.
WARNING: Host local has more than 0 drives of set. A host failure will result in data becoming unavailable.
MinIO Object Storage Server
Copyright: 2015-2023 MinIO, Inc.
License: GNU AGPLv3 <https://www.gnu.org/licenses/agpl-3.0.html>
Version: RELEASE.2023-01-25T00-19-54Z (go1.19.4 linux/amd64)

Status:         1 Online, 0 Offline.
API: http://10.244.2.131:9000  http://127.0.0.1:9000
Console: http://10.244.2.131:36649 http://127.0.0.1:36649

Documentation: https://min.io/docs/minio/linux/index.html
Warning: The standard parity is set to 0. This can lead to data loss.

score 2 · Answer 1 · answered Jan 25 '23 at 13:21

2

You can set the nodePort number inside the port config so that it won't be automatically set.

Try this Service:

apiVersion: v1
kind: Service
metadata:
  namespace: velero
  name: minio
  labels:
    component: minio
spec:
  type: NodePort
  ports:
    - port: 9000
      nodePort: 31481
      targetPort: 9000
      protocol: TCP
  selector:
    component: minio

answered Jan 25 '23 at 13:21

Amila Senadheera

12,229
15
27
43

Thanks for you help. Now Port number don't change but still I am not able to access my Application. – tauqeerahmad24 Jan 25 '23 at 13:26
Have you logged into one of the cluster nodes and trying? – Amila Senadheera Jan 25 '23 at 13:28
If you do `kubectl get nodes -o wide` it will show IPs of nodes? – Amila Senadheera Jan 25 '23 at 13:31
Yes, It assigned this pod to node 1 and I am using node 1 IP. I also login to node 1 and try there. both with localhost:31481 and Ipofnode1:31481. It shows site cant be reached. – tauqeerahmad24 Jan 25 '23 at 13:34
can you try port forwarding `kubectl port-forward svc/minio 9000:9000 -n velero` to check whether the service is running? also, have you set `- containerPort: 9000` in your deployment? – Amila Senadheera Jan 25 '23 at 13:37
Yes I changed the Ports and also updated my Question with full yaml. Maybe It help to find my mistakes. – tauqeerahmad24 Jan 25 '23 at 13:39
This is the output of kubectl port-forward Forwarding from 127.0.0.1:9000 -> 9000 Forwarding from [::1]:9000 -> 9000 . Still no access – tauqeerahmad24 Jan 25 '23 at 13:43
Let us [continue this discussion in chat](https://chat.stackoverflow.com/rooms/251386/discussion-between-tauqeerahmad24-and-amila-senadheera). – tauqeerahmad24 Jan 25 '23 at 13:49
That means your minio/minio container has not started the port. maybe due to some misconfiguration. can you check the logs of the pod? `kubectl logs -f minio- -n velero `. As updated question you should try port 9002 – Amila Senadheera Jan 25 '23 at 13:51
Just updated the Question again with logs. This time I can see some warnings. – tauqeerahmad24 Jan 25 '23 at 13:55
It seems it is exposing `9000` inside the container. So set `9000` instead of `9002` everywhere and try – Amila Senadheera Jan 25 '23 at 13:58
Sorry when I change it 9002 to 9000 I faced other issues. I had to reset my cluster. Now I used the default setting but still I faced the same issue. I updated the Logs of this container. – tauqeerahmad24 Jan 26 '23 at 11:59
When I see the logs of pod, There is console port is different than the nodePort. – tauqeerahmad24 Jan 27 '23 at 11:02

Why my Nodeport service change its port number?

1 Answers1

Linked