I have an application, running on Jetty Server and listening on port 8080. I have deployed it as a container. The application is running correctly and if I do curl -v http://127.0.0.1:8080 from within the pod, I get the correct response.

My pod also has an address. Lets call it 10.1.2.3 (hypothetical). If I try to do curl -v http://10.1.2.3:8080, I get a connection closed.

I tried changing the address on which my application starts to 10.1.2.3 and the curl works after that. However, I feel that defeats the purpose of containerization as I wouldn't have access to this IP before hand.

I also have a load balanced service, where I am mapping port 33000 to my service port 8080. The service was assigned a nodeport of 34000. Since this is running on my local docker, my aim was to do a curl -v http://localhost:34000 and reach my application, but that is obviously not happening.

Can some one please help as to what am I doing wrong? My definitions of the container and the service are given below:

resource.yaml

apiVersion: apps/v1
kind: Deployment
metadata:
  name: myapp-service-dev-pod1
  labels:
    app: myapp-service-dev
    component: myapp-service-dev
spec:
  selector:
    matchLabels:
      app: myapp-service-dev-pod1
  replicas: 2    
  template:
    metadata:
      labels:
        app: myapp-service-dev-pod1
        component: myapp-service-dev
    spec:
      volumes:
        - name: shared-dev-data
          emptyDir: {}
      containers:
        - name: myapp-service-dev-pod1
          image: docker/my-apps/mybuild_service:9
          ports:
            - containerPort: 8080
          volumeMounts:
            - name: shared-dev-data
              mountPath: /opt/myapp/jetty/logs

service.yaml

apiVersion: v1
kind: Service
metadata:
  name: myapp-service-dev-lb
  labels:
    app: myapp-service-dev
spec:
  ports:
    - port: 33000
      protocol: TCP
      name: http
      targetPort: 8080
  selector:
    component: myapp-service-dev
  type: LoadBalancer