if you add port, name, and protocol in the deployment spec, then you only need to run: kubectl expose deployment front-ed--type=NodePort --name=front-end-svc

This. is more align with the question k expose deployment front-end --name front-end-svc --type NodePort --port 80 --target-port HTTP

for reconfiguring part ; #kubectl edit deployment front-end then add the following in the container part; containers: - name: nginx-dep-cont image: nginx:1.14.2 ports: - name: http containerPort: 80 protocol: TCP and to Finally expose it; ## kubectl expose deployment front-end --name front-end-svc --target-port http --type=NodePort extra steps; # kubectl describe svc front-end-svc ## curl PICK-ANY-IP-FROM-ENDPOINTS:80 in my case # curl 192.168.133.201:80 Tested!

kubectl config use-context k8s kubectl expose deployment front-end --port=80 --target-port=80 --protocol=TCP --type=NodePort --name=front-end-svc with this solution it is much more easier

1 kubectl edit deploy front-end ports: - containerPort: 80 name: http 2 apiVersion: v1 kind: Service metadata: name: svc1 spec: selector: app: nginx ports: - name: name-of-service-port protocol: TCP port: 80 targetPort: http 3 apiVersion: v1 kind: Service metadata: name: svc2 type: NodePort selector: app: nginx ports: - port: 80 targetPort: http nodePort: 30007

which this one makes you think more than you need to answer. When asked to export (http) you can put a flag - name: http : example: ports: - container port: 80 name: http However, when you create the service and export port 80 from it.

The question as I understood: kubectl create deployment front-end --image=nginx --replicas=1 --dry-run=client -oyaml > dep1.yaml kubectl apply -f dep1.yaml vi dep1.yaml # manually add the name: http and containerPort: 80 kubectl expose deployment front-end --target-port=http --name=front-end-svc --type=ClusterIP/NodePort --dry-run=client -oyaml>svc1.yaml kubectl apply -f svc1.yaml kubectl describe svc front-end-svc

I dont realy understand if we need to do two or three actions- 1.reconfigure the yaml file - add ports. 2 create sa and 3. edit service adding type Nodeport or is it ok just reconfigure yaml and run k expose deployment front-end --name front-end-svc --type NodePort --port 80 --target-port HTTP ?

Who can explain the difference between these tasks: "T1. Create a new service named front-end-svc exposing the container port http. T2. Configure the new service to also expose the individual Pods via a NodePort on the nodes on which they are scheduled." Is it T1: first expose the deployment as default (service type ClusterIP is created) on port http? Then, T2, edit the service from type ClusterIP to type NodePort? I see the solutions mentioned here go directly to task 2. Quite confusing question.