Difference between revisions of "Exposing an External IP Address to Access an Application in a Cluster"
Jump to navigation
Jump to search
Tags: Mobile web edit, Mobile edit |
|||
Line 8: | Line 8: | ||
my-service LoadBalancer 172.20.165.35 a44a5217784174123143443.us-east-1.elb.amazonaws.com 3000:31896/TCP 19s | my-service LoadBalancer 172.20.165.35 a44a5217784174123143443.us-east-1.elb.amazonaws.com 3000:31896/TCP 19s | ||
+ | |||
+ | == Related == | ||
+ | * [[Kubernetes ingress]] | ||
== See also == | == See also == |
Revision as of 19:15, 27 March 2023
kubectl expose deployment hello-world --type=LoadBalancer --name=my-service service/my-service exposed
kubectl get services my-service NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE my-service LoadBalancer 172.20.165.35 a44a5217784174123143443.us-east-1.elb.amazonaws.com 3000:31896/TCP 19s
Related
See also
- 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: