title: Deployed kubernetes service from cluster is not accessible outside the cluster using node port method
body: <p>I am trying to access Kubernetes cluster deployed Spring Boot microservices and trying to test the REST API. I configured the node port method in my deployment scripts. But when I am trying to access using Postman tool, I am only getting the response that "Could not get any response".</p>
  
  <p>I configured the <strong>service.yaml</strong> script like the following structure,</p>
  
  <pre><code>apiVersion: v1
  kind: Service
  metadata:
    name: my-service
  spec:
    type: NodePort
    ports:
      - port: 7100
        targetPort: 7100
        protocol: TCP
        name: http
        nodePort: 31007
   selector:
        app: my-deployment
  </code></pre>
  
  <p>My <strong>deployment.yaml</strong> like the following ,</p>
  
  <pre><code>apiVersion: apps/v1
  kind: Deployment
  metadata:
    name: my-deployment
    labels:
      app: my-deployment
  spec:
    replicas: 1
    selector:
      matchLabels:
        app: my-deployment
    template:
      metadata:
        labels:
          app: my-deployment
        annotations: 
          date: "+%H:%M:%S %d/%m/%y"
      spec:
        imagePullSecrets:
          - name: "regcred"
        containers:
         - name: my-deployment-container
           image: spacestudymilletech010/spacestudysecurityauthcontrol:latest
           imagePullPolicy: Always
           ports:
              - name: http
                containerPort: 8065
                protocol: TCP
        tolerations:
        - key: "dedicated-app"
          operator: "Equal"
          value: "my-dedi-app-a"
          effect: "NoSchedule"
  </code></pre>
  
  <p>When I am taking <code>kubectl describe service</code>, output is like the following,</p>
  
  <p><a href="https://i.stack.imgur.com/Zwa9A.png" rel="noreferrer"><img src="https://i.stack.imgur.com/Zwa9A.png" alt="enter image description here"></a></p>
  
  <p>And I am trying to access my deployed api Like the following way,</p>
  
  <pre><code>  http://&lt;my-cluster-Worker-NodeIP-Address:31007/&lt;my-deployed-ReST-API-end-point&gt;
  </code></pre>
  
  <p><strong>Updates</strong></p>
  
  <p>When I am running the <code>kubectl describe pod</code> command for my deployment I am getting the response like the following,</p>
  
  <pre><code>docker@MILDEVKUB010:~$ kubectl describe pod spacestudycontrolalerts- 
  deployment-8644449c58-x4zd6
  Name:           spacestudycontrolalerts-deployment-8644449c58-x4zd6
  Namespace:      default
  Priority:       0
  Node:           &lt;none&gt;
  Labels:         app=spacestudycontrolalerts-deployment
              pod-template-hash=8644449c58
  Annotations:    date: +%H:%M:%S %d/%m/%y
  Status:         Pending
  IP:
  IPs:            &lt;none&gt;
  Controlled By:  ReplicaSet/spacestudycontrolalerts-deployment-8644449c58
  Containers:
    spacestudycontrolalerts-deployment-container:
      Image:        spacestudymilletech010/spacestudycontrolalerts:latest
      Port:         7102/TCP
      Host Port:    0/TCP
      Environment:  &lt;none&gt;
      Mounts:
    /var/run/secrets/kubernetes.io/serviceaccount from default-token-6s55b (ro)
  Conditions:
    Type           Status
    PodScheduled   False
  Volumes:
    default-token-6s55b:
      Type:        Secret (a volume populated by a Secret)
      SecretName:  default-token-6s55b
      Optional:    false
  QoS Class:       BestEffort
  Node-Selectors:  &lt;none&gt;
  Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
               node.kubernetes.io/unreachable:NoExecute for 300s
  Events:
    Type     Reason            Age        From               Message
    ----     ------            ----       ----               -------
    Warning  FailedScheduling  &lt;unknown&gt;  default-scheduler  0/2 nodes are available: 2 node(s) had taints that the pod didn't tolerate.
  </code></pre>
  
  <p>I am getting the event message from describe pod command like <code>0/2 nodes are available: 2 node(s) had taints that the pod didn't tolerate.</code> as shown above.</p>
  
  <p>When I am running <code>kubectl get nodes</code> command , I am getting like the following,</p>
  
  <pre><code>NAME           STATUS   ROLES    AGE   VERSION
  mildevkub020   Ready    master   5d    v1.17.0
  mildevkub040   Ready    master   5d    v1.17.0
  </code></pre>
  
  <p>Where have I gone wrong for service access?</p>