Difference between revisions of "Kubernetes LoadBalancer"
Jump to navigation
Jump to search
↑ https://kubernetes.io/docs/tutorials/stateless-application/expose-external-ip-address/
Line 16: | Line 16: | ||
* <code>[[NodePort]]</code> | * <code>[[NodePort]]</code> | ||
* [[ServiceTypes]] | * [[ServiceTypes]] | ||
− | * [[Kubernetes: Ingress controllers|Ingress controller]] | + | * [[Kubernetes: Ingress controllers|Ingress controller]]: <code>[[kind: Ingress]]</code> |
== See also == | == See also == |
Revision as of 15:02, 10 October 2023
Kubernetes LoadBalancer
exposes the Service externally using a cloud provider's load balancer.
kubectl expose deployment hello-world --type=LoadBalancer --name=my-service
[1]
Example
apiVersion: v1 kind: Service metadata: name: example-service spec: selector: app: example ports: - port: 8765 targetPort: 9376 type: LoadBalancer
Related
See also
- Understand ClusterIP, NodePort, LoadBalancer service types and endpoints
- Kubernetes networking: network policies, Network Policy Providers, CNI, Calico, flannel, Service mesh, Istio,
kube-proxy, coredns, AWS VPC CNI: vpc-cni
, Kubernetes: Ingress controllers, IPVS, ServiceTypes:LoadBalancer, ClusterIP, NodePort, ExternalName
, Endpoints, EndpointSlices, Kubernetes DNS,svc.cluster.local
, Weave Net
Advertising: