SIMULATION
Given a partially-functioning Kubernetes cluster, identify symptoms of failure on the cluster.
Determine the node, the failing service, and take actions to bring up the failed service and restore the health of the cluster. Ensure that any changes are made permanently.
You can ssh to the relevant I nodes (bk8s-master-0 or bk8s-node-0) using:
[student@node-1] $ ssh
You can assume elevated privileges on any node in the cluster with the following command:
[student@nodename] $ | sudo -i
Create 2 nginx image pods in which one of them is labelled with env=prod and another one labelled with env=dev and verify the same.
SIMULATION
Task
Schedule a pod as follows:
1.
Name: nginx-kusc00401
2.
Image: nginx
3.
Node selector: disk=ssd
SIMULATION
Task Monitor the logs of pod bar and: Extract log lines corresponding to error file-not-found
Write them to /opt/KUTR00101/bar
SIMULATION
Context
You have been asked to create a new ClusterRole for a deployment pipeline and bind it to a specific ServiceAccount scoped to a specific namespace.
Task
Create a new ClusterRole named deployment-clusterrole, which only allows to create the following resource types:
1.
Deployment
2.
StatefulSet
3.
DaemonSet
Create a new ServiceAccount named cicd-token in the existing namespace app-team1.
Bind the new ClusterRole deployment-clusterrole lo the new ServiceAccount cicd-token , limited to the namespace app-team1.
SIMULATION
Task
First, create a snapshot of the existing etcd instance running at https://127.0.0.1:2379, saving the snapshot to /srv/data/etcd-snapshot.db.
Next, restore an existing, previous snapshot located at /var/lib/backup/etcd-snapshot-previo us.db