I got a question to expose a deployment via nodeport with tcp port of 8888. But, . . .

Kubernetes
#1

Pradeep:
I got a question to expose a deployment via nodeport with tcp port of 8888. But, when I mention nodePort: 8888 in the yaml file. It says, it is not a standard range port. How could we resolve this?

#2

Tej_Singh_Rana:
Hello, @Pradeep
NodePort range between 30000 - 32767.

#3

Pradeep:
So, should I mention one of them of my own choice if they didn’t mention the port in the question

#4

Balaji K:
@Pradeep you will never specify a specific nodeport when creating. So you will always allow it to take and yes later you can edit via kube edit and update if question says a specific port.

#5

Pradeep:
got you. I am assuming we need to mention it always when creating service with nodeport.

#6

Tej_Singh_Rana:
No, that’s not necessary. Please give it a try in the lab.

#7

Tej_Singh_Rana:
Note - If you will not specify, then by default it will choose between 30000-32767.

#8

Pradeep:
Sure, thank you

#9

Joe:
What is the imperative command to create a nodeport service? I believe by default it chooses clusterip

#10

Pradeep:
@Joe

k expose deploy deployment-name --name=service-name --port=8888 --type=NodePort