Tweaking the Kubernetes Scheduling Algo | Day 8 | Taints-Tolerations, Affinity, QOS, OpenCost

Recap & Namespaces:

Namespaces can’t be nested(by default), this isn’t possible k8s but in GKE it’s possible.
kube-system: It’s reserved for k8s in-system components and working.
```
kubectl get pods -n kube-system
```
kube-node-lease: holds lease objects of node.

To check:

Here -n means we are specifying namespace
```
kubectl get lease -n kube-node-lease
```
Why kube-node-lease?

High Availability (HA) in Kubernetes ensures that the cluster remains operational even if some components fail. The kube-node-lease plays a crucial role in enhancing the efficiency of HA configurations in Kubernetes by optimizing node failure detection and reducing overhead.

Role of kube-node-lease in HA:
- Node Heartbeats via Leases
- Efficient Failure Detection
- Faster Failover
- Scalability for Large Clusters
- Want to read full?
No pod is created only lease object are.
```
kubetcl get pods -n kube-node-lease
```
Note: Number of nodes = Number lease objects
kube-public : Cluster usage
```
kubectl get pods -n kube-public
```
default:

It’ll show all the object that can be included in namspace:

kubectl api-resources --namespaced=true