image=nginx, image=redis, image=consul
Name nginx container as "nginx-container"
Name redis container as "redis-container"
Name consul container as "consul-container"
Create a pod manifest file for a container and append container
section for rest of the images
kubectl run multi-container --generator=run-pod/v1 --image=nginx --
dry-run -o yaml > multi-container.yaml
# then
vim multi-container.yaml
apiVersion: v1
kind: Pod
metadata:
labels:
run: multi-container
name: multi-container
spec:
containers:
- image: nginx
name: nginx-container
- image: redis
name: redis-container
- image: consul
name: consul-container
restartPolicy: Always

Solution:

See the solution below with Step by Step Explanation.
Explanation:
Solution (Step by Step) :
1. Create Roles for 'developer' and 'qa':


2. Create RoleBinding for 'developer' and 'qa':

3. Create ClusterRole for 'admin'.

4. Create ClusterRoleBindin for 'admin'.

We created separate roles (developer-role', 'cp-role') for each user group, limiting their access to specific namespaces and resources. We bound these roles to users using RoleBindings in the respective namespaces. For 'admin', we created a ClusterRole Cadmin-clusterrole') with full access to all resources, and bound it using a ClusterRoleBinding. This setup ensures that each user has appropriate access rights based on their role and responsibilities. ,

Solution:
#backup
ETCDCTL_API=3 etcdctl --endpoints="https://127.0.0.1:2379" --cacert=/opt/KUIN000601/ca.crt --cert=/opt/KUIN000601/etcd-client.crt --key=/opt/KUIN000601/etcd-client.key snapshot save /etc/data/etcd-snapshot.db
#restore
ETCDCTL_API=3 etcdctl --endpoints="https://127.0.0.1:2379" --cacert=/opt/KUIN000601/ca.crt --cert=/opt/KUIN000601/etcd-client.crt --key=/opt/KUIN000601/etcd-client.key snapshot restore /var/lib/backup/etcd-snapshot-previoys.db

See the solution below with Step by Step Explanation.
Explanation:
Solution (Step by Step) :
1. Update Deployment YAML:
- Update the 'spec.replicas' field to the desired number of replicas for the new version.
- In the 'spec.strategy.rollingUpdate' section, set the 'maxUnavailable' to 1, meaning that only one pod can be unavailable during the update process.
- Set the maxSurge' to 1, limiting the number of new pods that can be created simultaneously to 1.

2. Apply the Updated Deployment: - Use 'kubectl apply -f deployment.yaml' to apply the changes to your cluster. 3. Monitor the Update Process: - Use 'kubectl get pods -l app=my-app' to monitor the pods. You will see a rolling update in progress: - One old pod will be terminated at a time. - One new pod will be created at a time. - The update will continue until all replicas are updated to the new version. 4. Verify the Update: - Once the update is complete, use 'kubectl describe deployment my-deployment' to check the deployment status. The 'updatedReplicas' field should match the 'replicas' field, indicating that the update was successful. By using 'maxUnavailable' and 'maxSurge' you control the number of unavailable and surge pods during the update process. This ensures a safe and controlled rolling update strategy.,