Why ‘kubernetes’ service ?

DevOps
Posted on | by Sunilraj

MOTOSHARE 🚗🏍️
Turning Idle Vehicles into Shared Rides & Earnings

From Idle to Income. From Parked to Purpose.
Earn by Sharing, Ride by Renting.
Where Owners Earn, Riders Move.
Owners Earn. Riders Move. Motoshare Connects.

With Motoshare, every parked vehicle finds a purpose. Owners earn. Renters ride.
🚀 Everyone wins.

Start Your Journey with Motoshare

Analysis:

kubectl describe svc kubernetes

Name:              kubernetes
Namespace:         default
Labels:            component=apiserver
                   provider=kubernetes
Annotations:       <none>
<strong>Selector:          <none></strong>
<strong>Type:              ClusterIP</strong>
IP Family Policy:  SingleStack
IP Families:       IPv4
IP:                10.96.0.1
IPs:               10.96.0.1
Port:              https  443/TCP
TargetPort:        6443/TCP
<strong>Endpoints:         172.31.15.134:6443</strong>
Session Affinity:  None
Events:            <none>Code language: HTML, XML (xml)
  1. ‘kubernetes’ is a clusterIP service. (ie can be accessed only inside the cluster.)
  2. It has no selector specified.( So no automatic LB.)
  3. But endpoints specified(maybe hardcoded) as 172.31.15.134:6443 ( that means all the requests to this service will be routed to 172.31.15.134:6443)
  4. Now you can see the its the IP and port corresponding to APIServer pod.

Conclusion:

So kubernetes service act as a service for APIServer Pod.

Other pods inside the cluster like Scheduler, Controller etc, can use this service to communicate with APIServer pod.