Online Access Free CKAD Practice Test

See the solution below.
Explanation:
To find the broken pod and store its name and namespace to /opt/KDOB00401/broken.txt, you can use the kubectl get pods command and filter the output by the status of the pod.
kubectl get pods --field-selector=status.phase=Failed -o jsonpath='{.items[*].metadata.namespace}/{.items[*].
metadata.name}' > /opt/KDOB00401/broken.txt
This command will list all pods with a status of Failed and output their names and namespaces in the format
<namespace>/<pod>. The output is then written to the /opt/KDOB00401/broken.txt file.
To store the associated error events to a file /opt/KDOB00401/error.txt, you can use the kubectl describe command to retrieve detailed information about the pod, and the grep command to filter the output for error events.
kubectl describe pods <pod-name> --namespace <pod-namespace> | grep -i error -B5 -A5 > /opt/KDOB00401
/error.txt
Replace <pod-name> and <pod-namespace> with the name and namespace of the broken pod you found in the previous step.
This command will output detailed information about the pod, including error events. The grep command filters the output for lines containing "error" and also prints 5 lines before and after the match.
To fix the issue, you need to analyze the error events and find the root cause of the issue.
It could be that the application inside the pod is not running, the container image is not available, the pod has not enough resources, or the liveness probe configuration is incorrect.
Once you have identified the cause, you can take appropriate action, such as restarting the application, updating the container image, increasing the resources, or modifying the liveness probe configuration.
After fixing the issue, you can use the kubectl get pods command to check the status of the pod and ensure

See the solution below with Step by Step Explanation.
Explanation:
Solution (Step by Step) :
1. Define the Horizontal Pod Autoscaler (HPA) YAMLI
- Create an HPA YAML file named 'auto-scaler.yaml' with the following contents:

2. Apply the HPA: - Apply the HPA YAML file using 'kubectl apply -f auto-scaler.yamr. 3. Test the Auto-scaler - Monitor the CPU utilization of your deployment. When it exceeds 70%, the HPA will automatically scale up the deployment. - Observe the deployment scaling down when CPIJ utilization drops below 50%.

See the solution below with Step by Step Explanation.
Explanation:
Solution (Step by Step) :
1. Define the Vehicle Custom Resource Definition (CRD):
- Create a YAML file named 'vehicle-crd-yaml with the following content:

2. create the CRD: - Apply the CRD definition using 'kubectl apply -f vehicle.crd.yaml'. 3. Validate the CRD: - Verity that the CRD is created successfully by running kubectl get crd vehicles-example.com'. 4. Create a Vehicle Resource: - Create a YAML file named 'vehicle-yamr with the following content:

5. Create the Vehicle Resource: - Apply the vehicle resource definition using 'kubectl apply -f vehicle-yamr 6. Verify the Vehicle Resource: - Ensure that the vehicle resource is created successfully by running 'kubectl get vehicles -n default 7. Update the 'status' Field: - Attempt to update tne 'status' field directly using 'kubectl patch vehicle vehicle-I -n default -p '{"spec": {"status": "driving"))" - Observe that the update fails because the 'status' field is considered immutable and can only be updated by the controller managing the vehicles. 8. Implement a Controller: - Create a controller that reads the 'Vehicles resources, updates the 'status' field based on the vehicle's state, and handles any errors. This controller should have read-only access to the 'spec' field and write access to the 'status' field. 9. Deploy the Controller: - Deploy the controller as a Deployment or a StatefulSet in Kubernetes- 10. IJpdate the 'status' Field through the Controller. - Trigger the controller to update the 'status' field of the 'vehicle-1' resource. - Verot that the 'status' field is updated successfully without violating the immutability rule. Key Points: - The CRD defines the 'Vehicle' resource schema and its required fields. - The 'status' field is marked as immutable to prevent direct updates by users- -A controller is responsible for updating the 'status' field based on the vehicle's state and ensuring data integrity. - This setup ensures that the 'status' field is always consistent and updated by the designated controller, maintaining data integrity and preventing accidental modifications.,

See the solution below with Step by Step Explanation.
Explanation:
Solution (Step by Step) :
1. Create a CronJob YAML file:

2. Apply the Cronjob: bash kubectl apply -f image-cleanup-cronjob.yaml 3. Verify the CronJob: bash kubectl get cronjobs - Schedule: The 'schedule' field defines the cron expression, which triggers the job every day at 10:00 AM. - Job Template: - The 'j0bTemplate' defines the actual job that Will be executed. - Container: - The 'image' field specifies the container image to use. In this case, it's a container with 'kubectr pre-installed_ - The 'command' and Sargs' fields detine the command to run in the container. The command uses 'kubectr to list images With the specified label and then iterates through them, checking their creation date. If an image is older than 7 days, it's deleted. - RestaftPolicy: The 'restartPolicy' is set to 'OnFailure' to ensure the job restarts if it fails. Important Note: - Make sure the container image you choose has the necessary tools (like 'kubectl') to interact with your Kubernetes cluster. - This solution assumes you have the necessary permissions to delete images. If not, you may need to modify the 'kubectl delete image' command to use appropriate RBAC roles. - This solution doesn't consider images used by running pods. You should adjust the script to exclude images that are currently in use. This Cronjob will automatically run every day, cleaning up old container images and maintaining a clean environment in your cluster.,

See the solution below with Step by Step Explanation.
Explanation:
Solution (Step by Step) :
1. Create a base Kustomization file:
resources :
- deployment. yaml
2. Create a deployment-yaml file:

3. Create environment-specific overlays: - For dev environment

- For prod environment:

4. Create a patch.yaml file:

5. Apply Kustomize: - For dev environment: bash Kustomize dev I oubect1 apply -f - - For prod environment: bash Kustomize prod I oubect1 apply -f - - The base customization file defines the resources that are included in the deployment. - The environment-specific overlays patch the base resources With the appropriate image tag. - The patchesStrategicMerge' field applies the patch.yaml tile to the deployment. - The '{{.environment}Y placeholder in the patch file is replaced with the actual environment name when Kustomize is applied. This approach allows you to easily manage and deploy your applications to different environments with specific configuration settings.