Difference between revisions of "LoadBalancer:"
Jump to navigation
Jump to search
↑ https://kubernetes.io/docs/concepts/services-networking/service/#loadbalancer
| (One intermediate revision by the same user not shown) | |||
| Line 18: | Line 18: | ||
[[rules:]] | [[rules:]] | ||
| + | |||
| + | [[status:]] | ||
| + | [[loadBalancer:]] {} | ||
| + | |||
| + | == Related == | ||
| + | * <code>[[minikube addons enable ingress]]</code> | ||
== See also == | == See also == | ||
Latest revision as of 15:43, 27 November 2023
kind: Ingress
apiVersion: v1[1] kind: Service metadata: name: my-service spec: selector: app.kubernetes.io/name: MyApp ports: - protocol: TCP port: 80 targetPort: 9376 clusterIP: 10.0.171.239 type: LoadBalancer status: loadBalancer: ingress: - ip: 192.0.2.127
.../... status: loadBalancer: ingress: - hostname: a324242432.elb.ap-southeast-1.amazonaws.com .../...
.../...
status:
loadBalancer: ingress: - ip: 10.10.10.1 - ip: 10.10.10.2
.../...
rules:
status: loadBalancer: {}
Related[edit]
See also[edit]
kind:[Pod | Ingress | ClusterConfiguration|Config | ConfigMap | ServiceAccount | Deployment | List | Secret | Status ], spec: metadata: data:- Ingress controllers, NGINX Ingress Controller,
minikube addons enable ingress,kubectl get ingress, kubectl get ingressclass, kubectl describe ingress,Ingress:, Ingress API, AWS Load Balancer Controller, Envoy Proxy, GKE Ingress, Kubernetes Gateway API,ingress.k8s.aws, ingresses.networking.k8s.io,kind: Ingress: (tls:, hosts:),SuccessfullyReconciled
Advertising:
