Scaling the Deployment using kubectl

# Check the Deployment replicas
kubectl get deployments
# Output example:
# NAME            READY   UP-TO-DATE   AVAILABLE   AGE
# Find the LoadBalancer’s public IP
kubectl get service
# NAME            TYPE           CLUSTER-IP      EXTERNAL-IP     PORT(S)         AGE
# kodekloudapp    LoadBalancer   10.0.199.121    20.247.251.108  80:30895/TCP    73m
# kubernetes      ClusterIP      10.0.0.1        <none>          443/TCP         124m

kubectl scale deployment kodekloudapp --replicas=5
kubectl get deployment kodekloudapp
# NAME            READY   UP-TO-DATE   AVAILABLE   AGE
# kodekloudapp    5/5     5            5           76m

kubectl scale deployment kodekloudapp --replicas=30
kubectl get deployment kodekloudapp
# NAME            READY   UP-TO-DATE   AVAILABLE   AGE
# kodekloudapp    16/30   30           16          78m

kubectl get pods
# NAME                           READY   STATUS    RESTARTS   AGE
# kodekloudapp-677fc758c5-5k92g  0/1     Pending   0          57s
# kodekloudapp-677fc758c5-bbp84  0/1     Pending   0          57s
# ...

kubectl get pods --field-selector=status.phase!=Running

kubectl describe pod kodekloudapp-677fc758c5-5k92g

Warning  FailedScheduling   2m     default-scheduler   0/1 nodes are available: 1 Too many pods.
Normal   NotTriggerScaleUp  110s   cluster-autoscaler  max node group size reached

kubectl get namespaces
# NAME              STATUS   AGE
# default           Active   129m
# kube-node-lease   Active   129m
# kube-public       Active   129m
# kube-system       Active   129m

kubectl get pods --namespace kube-system
# NAME                                               READY   STATUS    RESTARTS   AGE
# ama-logs-rs-7f8bcb7c6f-5dlqq                       1/1     Running   0          131m
# coredns-59b6bf8b4f-lwt4c                           1/1     Running   0          131m
# metrics-server-7d74d8758-wfsdd                     2/2     Running   0          130m
# ...