K
Q

Question

Can't connect to Kubernetes Cluster on external IP

8/27/2018

I'm trying to access .NET Web API which I docker-ized and mounted in an Kubernet Cluster on Microsoft Azure.

The application works fine on local docker machine. The cluster is running, my deployment was correct and the pods where created. Everything I check is fine, but I cannot access my application through the external cluster IP (Load Balancer). This is my YAML deployment file:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: ohmioapi-deployment
spec:
  selector:
    matchLabels:
      app: ohmioapi
  replicas: 1
  template:
    metadata:
      labels:
        app: ohmioapi
    spec:
      containers:
      - name: ohmioapi
        image: ohmiocontainers.azurecr.io/ohmioapi:latest
        imagePullPolicy: Always
        ports:
        - containerPort: 15200
      imagePullSecrets:
        - name: acr-auth
---
apiVersion: v1
kind: Service
metadata:
  name: ohmioapi
  labels:
    app: ohmioapi
spec:
  selector:
    app: ohmioapi
  ports:
  - port: 15200
    nodePort: 30200
    protocol: TCP
  type: LoadBalancer

Can anyone give a hint of where to start looking for? Thanks!

-- ericpap

azure

kubernetes

3 Answers

8/27/2018

Pretty sure you need 'targetport' instead of 'nodeport' (or just drop it if the port is the same).

https://kubernetes.io/docs/concepts/services-networking/service/#loadbalancer

-- 4c74356b41

Source: StackOverflow

8/28/2018

You can use the command kubectl get service to get all the information of services and check your service ohmioapi, the result will like this:

Or you can use the command kubectl describe service serviceName to get more details about your service, the result will like this:

You can check the port mapping in the load balancer and access from the browser via the external IP and port.

You also can use the command kubectl edit service serviceName to edit and check from the config file created by the Kunernetes, the result will like this:

-- Charles Xu

Source: StackOverflow

8/27/2018

I would give the deployment/pods port a name (e.g. http) and then make the service serve off port 80 but target the pod port by name... that way you don't have to worry about port numbers when connecting to a service.

Also, you shouldn't need or want to use nodePort if you are using type of LoadBalancer.

E.g.

apiVersion: apps/v1
kind: Deployment
metadata:
  name: ohmioapi-deployment
spec:
  selector:
    matchLabels:
      app: ohmioapi
  replicas: 1
  template:
    metadata:
      labels:
        app: ohmioapi
    spec:
      containers:
      - name: ohmioapi
        image: ohmiocontainers.azurecr.io/ohmioapi:latest
        imagePullPolicy: Always
        ports:
        - name: http
          containerPort: 15200
      imagePullSecrets:
        - name: acr-auth

---
apiVersion: v1
kind: Service
metadata:
  name: ohmioapi
  labels:
    app: ohmioapi
spec:
  selector:
    app: ohmioapi
  ports:
  - name: http
    port: 80
    targetPort: http
    protocol: TCP
  type: LoadBalancer

-- Charlino

Source: StackOverflow

KQ

Can't connect to Kubernetes Cluster on external IP

Similar Questions

3 Answers

K
Q