Y53. Chapter III kubernetes from introduction to mastery -- ingress (26)

10.ingres Use cases

10.1 Kubernetes service Several types

# kubectl explain service.spec.type

ClusterIP： The default type , be used for k8s Internal service access , That is, through internal service ip Realize the access between services ,service IP Can only be accessed internally , Cannot access... From outside .

NodePort： stay cluster IP Based on , Through in each node The node listens to a host port that can be specified (nodePort) To expose the service , Thus allowing external client visit k8s Services in the cluster ,nodePort Put the outside client Forward your request to service To deal with .

LoadBalancer： Mainly in public clouds such as Alibaba cloud 、AWS Upper use ,LoadBalancer Builds on the nodePort On the basis of , The load balancer provided by the public cloud service provider will k8s The services in the cluster are exposed to those outside the cluster client visit .

ExternalName： Is used to k8s Services outside the cluster are mapped to k8s Cluster internal access , So as to make pod Can pass through fixed service name Access services outside the cluster , Sometimes it is also used to make different namespace Between pod adopt ExternalName Visit .

Service  If it is cluster  Type then from clusterIP  To pod  The default is TCP  agreement ,TCP  Support MySQL、Redis  And other specific services , And then there is UDP  and SCTP  agreement .

Kubernetes Several ways to expose Services ：
NodePort

cluster