Difference between revisions of "Kubectl expose deployment"
Jump to navigation
Jump to search
↑ https://kubernetes.io/docs/tutorials/stateless-application/expose-external-ip-address/
Tags: Mobile web edit, Mobile edit |
|||
| (2 intermediate revisions by the same user not shown) | |||
| Line 23: | Line 23: | ||
== Related == | == Related == | ||
* [[DNS-1035]] | * [[DNS-1035]] | ||
| + | * <code>[[kind: Ingress]]</code> | ||
== See also == | == See also == | ||
* {{kubectl expose}} | * {{kubectl expose}} | ||
| + | * {{K8s net}} | ||
[[Category:K8s]] | [[Category:K8s]] | ||
Latest revision as of 08:06, 23 February 2024
kubectl expose deployment kubectl expose deployment nginxapp --name=nginxclusterip --port=80 --target-port=8080
kubectl expose deployment kubernetes-dashboard -n kube-system --type=NodePort
Create a external LB, in AWS AWS LB, to provide external access to your application:
kubectl expose deployment hello-world --type=LoadBalancer --name=my-service [1]
Verify:
kubectl get services my-service NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE my-service ClusterIP 172.20.251.125 <none> 80/TCP 3d5h
if EXTERNAL-IP address is not assigned verify that aws-load-balancer-controller is installed.
Activities[edit]
- Understand the differences between:
kubectl create service loadbalancerandkubectl expose deployment
Related[edit]
See also[edit]
kubectl expose [ deployment | pod ]- 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:
