Difference between revisions of "NodePort"
Jump to navigation
Jump to search
↑ https://kubernetes.io/docs/concepts/services-networking/service/#publishing-services-service-types
| Line 13: | Line 13: | ||
* <code>[[kubectl describe services mylbservice]]</code> | * <code>[[kubectl describe services mylbservice]]</code> | ||
* [[ExternalName]] | * [[ExternalName]] | ||
| + | * [[type: NodePort]] | ||
== See also == | == See also == | ||
Latest revision as of 17:59, 15 February 2024
NodePort exposes the Service on each Node's IP at a static port (the NodePort). To make the node port available, Kubernetes sets up a cluster IP address, the same as if you had requested a Service of type: ClusterIP.[1]
NodePort exposes the Service on the same port of each selected Node in the cluster using NAT. Makes a Service accessible from outside the cluster using <NodeIP>:<NodePort>. Superset of ClusterIP.
https://kubernetes.io/docs/tutorials/kubernetes-basics/expose/expose-intro/
kubectl create nodeport
Related[edit]
ClusterIPLoadBalancer- CKA 1.23, CKA 1.24 Understand ClusterIP, NodePort, LoadBalancer service types and endpoints
kubectl describe services mylbservice- ExternalName
- type: NodePort
See also[edit]
- NodePort,
kubectl create nodeport - Kubernetes services,
kubectl get services, kubectl describe service,kubectl create service[loadbalancer|nodeport|clusterip|externalname ], kubectl expose,headless service, service.beta.kubernetes.io
Advertising:
