Shulou(Shulou.com)06/02 Report--

My previous article on how to create an Nginx service in Kubernetes describes how to create a Kubernetes pod and service using the kubectl run command.

This article describes another way to learn how pods and corresponding services are bound in Kubernetes.

First create a deployment named jerry-nginx-1982 using the following command line:

kubectl create deployment jerry-nginx-1982 --image=nginx

Then use kubectl to get deployment to get the deployment created:

Then create a service with the same name, of type nodeport.

kubectl create service nodeport jerry-nginx-1982 --tcp 80:80

After the creation is complete, use the command line kubectl get svc to get the exposed port number named jerry-nginx-1982:31954:

Then you can access nginx server via this port number:

So how are these two namesake pods and services related?

First open the kubernetes dashboard and find the pod you created earlier:

Details: jerry-nginx-1982-67cb658cb8-9hl99

Open the service with the same name:

Then open the pod in this service and find that it is jerry-nginx-1982-67cb658cb8-9hl99 we found earlier, indicating that pod and service are associated by name.

We can do a negative test by creating a service called test without creating a pod called test beforehand:

kubectl create service nodeport test --tcp 80:80

After the service is created successfully, open this service and find that there is no pod assigned to it:

This result is consistent with our prediction.

To get more Jerry's original articles, please pay attention to the public account "Wang Zixi":

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.