Difference between revisions of "ClusterIP"
Jump to navigation
Jump to search
↑ https://kubernetes.io/docs/concepts/services-networking/service/#publishing-services-service-types
(One intermediate revision by the same user not shown) | |||
Line 1: | Line 1: | ||
− | <code>ClusterIP</code> | + | <code>ClusterIP</code> [[exposes]] the Service on a cluster-internal IP. Choosing this value makes the Service only reachable from [[within the cluster]]. This is the default that is used if you don't explicitly specify a type for a Service. <ref>https://kubernetes.io/docs/concepts/services-networking/service/#publishing-services-service-types</ref> |
Line 20: | Line 20: | ||
* <code>[[kind: Endpoint]]</code> | * <code>[[kind: Endpoint]]</code> | ||
* [[CLUSTER-IP]] | * [[CLUSTER-IP]] | ||
+ | * [[spec.clusterIPs]] | ||
== See also == | == See also == |
Latest revision as of 13:57, 13 December 2023
ClusterIP
exposes the Service on a cluster-internal IP. Choosing this value makes the Service only reachable from within the cluster. This is the default that is used if you don't explicitly specify a type for a Service. [1]
kubectl create clusterip
kubectl get service | grep ClusterIP
kubectl get all
Redis values.yml[edit]
Related[edit]
NodePort
externalName
- CKA 1.23 Understand ClusterIP, NodePort, LoadBalancer service types and endpoints
kubectl get services
kubectl port-forward
kind: Service
kind: Endpoint
- CLUSTER-IP
- spec.clusterIPs
See also[edit]
- Kubernetes services,
kubectl get services, kubectl describe service
,kubectl create service
[loadbalancer
|nodeport
|clusterip
|externalname ], kubectl expose
,headless service, service.beta.kubernetes.io
- 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: