Scheduling Pods with Taints and Tolerations in Kubernetes

1. Use the following command to taint the node:

kubectl taint node <node_name> node-type=prod:NoSchedule

1. Use the following YAML to specify a pod that will be scheduled to the dev environment:

   apiVersion: v1
   kind: Pod
   metadata:
     name: dev-pod
     labels:
       app: busybox
   spec:
     containers:
     - name: dev
       image: busybox
       command: ['sh', '-c', 'echo Hello Kubernetes! && sleep 3600']
   

1. Use the following command to create the pod:

  ```
  kubectl create -f dev-pod.yaml
  ```

1. Use the following YAML to create a deployment and a pod that will tolerate the prod environment:

   apiVersion: apps/v1
   kind: Deployment
   metadata:
     name: prod
   spec:
     replicas: 1
     selector:
       matchLabels:
         app: prod
     template:
       metadata:
         labels:
           app: prod
       spec:
         containers:
         - args:
           - sleep
           - "3600"
           image: busybox
           name: main
         tolerations:
         - key: node-type
           operator: Equal
           value: prod
           effect: NoSchedule
   

2. Use the following command to create the pod:

   kubectl create -f prod-deployment.yaml
   

1. Use the following command to verify the pods have been scheduled:

   kubectl get pods -o wide
   

2.Scale up the deployment:

   kubectl scale deployment/prod --replicas=3

3. Verify the toleration of the production pod:

   kubectl get pods <pod_name> -o yaml