Kuber API Server
March 12, 2026

đ Kube API Server áááŻáᏠááŹáá˛?
đŻ Kube API Server = Kubernetes áá˛áˇ áŚá¸áážáąáŹááş (Brain) â Cluster áá˛áˇ component áĄáŹá¸ááŻáśá¸áá˛áˇ áááşáá˝ááşááźáŽá¸ orchestrate ááŻááşáááˇáş central hub
đŚ Basic Info
- **Type: **RESTful API (HTTP/HTTPS)
- **Location: **Master Node
- **Port: **6443 (HTTPS)
- **Role: **Kubernetes cluster áá˛áˇ single entry point
âď¸ API Server áá˛áˇ áĄááá ááŹáááşááťáŹá¸ (5 Functions)
1. Authentication (áááşáá°? á á áşááąá¸ááźááşá¸)
- Request ááąá¸ááŹáá˛áˇáá° áááşáá°áᲠá á áşááąá¸áááş
- Methods: Certificates, Tokens, Basic Auth
2. Authorization (ááŹááŻááşáá˝ááˇáşáážá? á á áşááąá¸ááźááşá¸)
- RBAC (Role-Based Access Control)
- User/ServiceAccount áážáŹ permission áážáááŹá¸?
3. Admission Control (Policy á á áşááąá¸ááźááşá¸)
- Object ááᯠcreate/modify áááŻááşáááş policies á á áşááąá¸áááş
- áĽáááŹ: Resource limits set áááŹá¸áááş block ááŻááşáááş
4. Validation & Serialization
- Request data format áážááşáááşáážáŻ á á áşááąá¸áááş
- Object ááᯠJSON/Protobuf format ááźááˇáş serialize ááŻááşáááş
5. etcd Communication (áá áşááŻáááşá¸ááąáŹ etcd gateway)
- etcd ááᯠread/write ááŻááşáá˝ááˇáş áážáááąáŹ áá áşááŻáááşá¸ááąáŹ component
- Scheduler, Controller áááŻáˇ etcd ááᯠáááŻááşáááŻááş access áááá°á¸
đ Request Flow (kubectl apply ááŻááşáá˛áˇ áĄááŤ)
kubectl apply -f pod.yaml
Step 1: kubectl â API Server (HTTPS:6443)
Step 2: API Server â Authentication (áááşáá°?)
Step 3: API Server â Authorization (RBAC - áá˝ááˇáşááźáŻááŹá¸?)
Step 4: API Server â Admission Control (policies OK?)
Step 5: API Server â Validate object
Step 6: API Server â etcd (save desired state)
Step 7: API Server â Scheduler (pod ááᯠnode áá˝á˛ááąá¸ááŤ)
Step 8: Scheduler â API Server (node X áážáŹ run ááŤ)
Step 9: API Server â etcd (update scheduling info)
Step 10: API Server â kubelet on worker node
Step 11: kubelet â containerd (container create)
Step 12: kubelet â API Server (status update)
Step 13: API Server â etcd (update actual state)
đ Real-World Analogy
đ˘ Kubernetes = ááŻáášáááŽááźáŽá¸
API Server = Company áá˛áˇ Receptionist + Security + CEO
⢠áááşáá° áááşááŹááŹáᲠá á áşáááş (Authentication)
⢠ááŹááŻááşáááŻááşáá˝ááˇáş áážááᲠá á áşáááş (Authorization)
⢠CEO áᎠmessage áááşááąá¸áááş (etcd/controllers)
⢠Worker áá˝áąááᯠtask ááąá¸áááş (kubelet)
API Server áááŤááťážááş = ááŻáášááᎠoperate áááŻááşáááŻááşááąáŹáˇ!
đ ď¸ Practical Commands
# API Server pod ááźááˇáşáááş
kubectl get pods -n kube-system | grep kube-apiserver
# API Server status
kubectl describe pod kube-apiserver-master -n kube-system
# API Server manifest (kubeadm)
cat /etc/kubernetes/manifests/kube-apiserver.yaml
# Direct API call (bypass kubectl)
curl -k https://localhost:6443/api/v1/pods \
--cacert /etc/kubernetes/pki/ca.crt \
--cert /etc/kubernetes/pki/apiserver-kubelet-client.crt \
--key /etc/kubernetes/pki/apiserver-kubelet-client.key
# Check API Server health
kubectl get componentstatuses
curl -k https://localhost:6443/healthz
âď¸ Important Flags (kube-apiserver config)
# /etc/kubernetes/manifests/kube-apiserver.yaml
--etcd-servers=https://127.0.0.1:2379 # etcd address
--service-cluster-ip-range=10.96.0.0/12 # Service IP range
--authorization-mode=Node,RBAC # Auth methods
--advertise-address=192.168.1.10 # API Server IP
--secure-port=6443 # HTTPS port
--tls-cert-file=/etc/kubernetes/pki/apiserver.crt
--tls-private-key-file=/etc/kubernetes/pki/apiserver.key
đ Summary Table
- **Type: **RESTful API server
- **Location: **Master node
- **Port: **6443 (HTTPS)
- **Auth Methods: **Certificates, Tokens, OIDC
- **etcd Access: **Only component with direct access
- **Manifest: **/etc/kubernetes/manifests/kube-apiserver.yaml
đ CKA Exam Tips:
⢠API Server manifest path áážááşááŹá¸ááŤ
⢠Authentication vs Authorization áá˝á˛ááŹá¸áááşááŤ
⢠API Server down ááźá áşáááş kubectl á run áááŻááşááąáŹáˇáá°á¸
⢠kubeconfig file: ~/.kube/config (API Server address ááŤáááş)