You can easily check it by yourself looking at the service you've just created: kubectl get svc site-web -o yamlĪnd you'll see something like this in spec.ports section: - nodePort: 32576Īfter exposing your Pod (or Deployment) properly i.e. If you provide only -port=8080 flag to your kubectl expose command it assumes that the target-port's value is the same as value of -port. Your kubectl expose command may look like this: kubectl expose pod site-web -type=LoadBalancer -port=8080 -target-port=80 Note that your container exposes port 80, not 8080 ( containerPort: 80 in your container specification) so you need to specify it as target-port in your Service. However you can still use it just for exposing a single Pod. If you have a Deployment which typically manages a set of Pods between which the real load can be balanced, LoadBalancer does its job.
Of course you can, however exposing a single Pod via LoadBalancer Service doesn't make much sense.
But I cannot use for example: kubectl expose pod site-web -type=LoadBalancer -port=8080
