Keep same loadbalancer when redeploying pods

Question

I deployed a web server on a pod and created a load balancing service like this kubectl expose deployment api --port=80 --target-port=8080 --name api-LB --type=LoadBalancer

However when I re-deployed the pod, let's say with some updates, it seems that loses the binding with the LoadBalancer. So I have to create a loadbalancing service from the top so to get an external ip.

I would like to ask, if there is a way to bind the Load Balancer and the pod so there won't be any need for exposing the pod to the loadbalancer each time new pod deployments are performed.

API development yaml

apiVersion: apps/v1
kind: Deployment
metadata:
  name: api-dev
  namespace: default
spec:
  template:
    metadata:
      name: api-dev

    spec:
      volumes:
      - name: nfs-volume
        nfs:
          # URL for the NFS server
          server: xxxx
          path: xxxx

      containers:
      - name: api-dev
        image: docker-image-at-registry
        ports:
          - containerPort: 80
            name: server

        volumeMounts:
          - name: nfs-volume
            mountPath: /var/nfs

      imagePullSecrets:
        - name: regcred

  replicas: 1
  selector:
    matchLabels:
      app.kubernetes.io/name: api-dev

  strategy:
    type: RollingUpdate
    rollingUpdate:
      maxSurge: 1
      maxUnavailable: 0

Which version of Kubernetes did you use and how did you set up the cluster? Did you use bare metal installation or some cloud providor? It is important to reproduce your problem. — Mikołaj Głodziak, Nov 23 '21 at 11:00
Hello @MikołajGłodziak, I am using VMware's PKS. NVM I found a solution with deploying a load balancer service for a specific application. Thanks for your time tho :) — Ioan Kats, Mar 15 '22 at 22:02

quoc9x · Answer 1 · 2021-11-23T14:16:00.750

0

You have to add the label in deploymet api?
Something look like:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: api-dev
  namespace: default
spec: 
  template:
    metadata:
      name: api-dev
      labels:
        app: api-dev

    spec:
      volumes:
      - name: nfs-volume
        nfs:
          # URL for the NFS server
          server: xxxx
          path: xxxx

      containers:
      - name: api-dev
        image: docker-image-at-registry
        ports:
          - containerPort: 80
            name: server

        volumeMounts:
          - name: nfs-volume
            mountPath: /var/nfs

      imagePullSecrets:
        - name: regcred

  replicas: 1
  selector:
    matchLabels:
      app.kubernetes.io/name: api-dev
      app: api-dev

  strategy:
    type: RollingUpdate
    rollingUpdate:
      maxSurge: 1
      maxUnavailable: 0

Then, try this

kubectl expose deployment api --port=80 --target-port=8080 --name api-LB --type=LoadBalancer --selector=app=api-dev

edited Nov 23 '21 at 14:16

answered Nov 23 '21 at 07:52

quoc9x

1,423
2
9
26

Hello, just shared the deployment file as well – Ioan Kats Nov 23 '21 at 09:53
Thanks for your answer, but I get ```error. unexpected label spec: api-dev``` – Ioan Kats Nov 23 '21 at 10:03
Have you added the label to the yaml file? – quoc9x Nov 23 '21 at 10:04
Which labels ? I tried the expose command that you provided above – Ioan Kats Nov 23 '21 at 10:16
I just edited my answer. Can you try again? – quoc9x Nov 23 '21 at 10:25
1

use --selector=app=api-dev like this : `kubectl expose deployment api --port=80 --target-port=8080 --name api-LB --type=LoadBalancer --selector=app=api-dev` – gohm'c Nov 23 '21 at 12:48
Oh right, I was a little confused. I have slightly edited the my answer. – quoc9x Nov 23 '21 at 14:15
Have you solved your problem yet? – quoc9x Nov 23 '21 at 14:41

Keep same loadbalancer when redeploying pods

1 Answers1