Is it possible for LoadBalancer type Service not to allocate a NodePort?

DevOps Kubernetes
#1

Hi,

is it possible for LoadBalancer type Service not to allocate a NodePort?

#2

No, because then there’d be no way for the traffic to hit the host.

#3

Ok in that case if we want take snapshot of namespace and restore it to another new namespace, then we can’t do this.

it would give error i.e. nodeport is already allocated

#4

I guess I’ll take your word for it. Have you tried with Velero?

#5

no i am using portworx

#6

Then you have commercial support, so you should take it up with them.

#7

okay and also if i restore the snapshot is same namespace using portworx it is changing and assigning new external IP, even though
i am giving LB ip in manifest

loadBalancerIP: . Is there any way we can set default IP that never change?

#8

You don’t need to keep mentioning me, I see your responses.

#9

You need to talk to Pure support.

#10

Okay will keep in mind for next time

#11

Thanks for the guidance!