Linux Foundation CKAD Value Pack (Frequently Bought Together)

Correct Answer:

See the solution below with Step by Step Explanation.
Explanation:
Solution (Step by Step) :
1. Define a CRD for Secret Access:
- Create a Custom Resource Definition (CRD) named 'SecretAccess' , representing the required access to the Secret. This CRD will define the following fields:
- 'secretName': The name ot the Secret containing the sensitive information.
- 'allowedKeys': A list of keys from the Secret that the application is allowed to access.
- The 'SecretAccess' CRD schema will be validated to ensure that the specified Secret and keys exist.

2. Create a Controller for SecretAccess CRD. - Implement a Kubernetes controller that watches for changes in 'SecretAccesS resources. - When a new 'SecretAccesS resource is created or updated, the controller: - Validates the specified Secret and allowed keys. - Creates or updates a new 'Secret resource with the requested keys from the original Secret. - Updates the 'SecretAccess' resource status with the name of the generated Secret.

3. Create a SecretAccess Resource: - Define a 'SecretAccess' resource specifying the target Secret and allowed keys.

4. Update the Application to IJse the Generated Secret: - Modify your application to use the generated Secret, whiCh will contain only the allowed keys. - The generated Secret name can be retrieved from the "SecretAccess' resource status. - The application can access the Secret using the Kubernetes API, similar to accessing a regular Secret.

- The SecretAccesS CRD acts as a resource request for access to specific keys from a Secret_ - The controller ensures that only the requested keys are made available to the application, enhancing security. - By generating a separate Secret for each application with limited access, you prevent accidental exposure ot sensitive data. - The automated update mechanism of the controller allows you to update the original Secret without disrupting the application.,

Correct Answer:

See the solution below with Step by Step Explanation.
Explanation:
Solution (Step by Step) :
1. Update the Deployment YAML:
- Update the 'replicas to 2_
- Define 'maxunavailable: 1 ' and 'maxSurge: 1 ' in the 'strategy.rollingupdate' section to control the rolling update process.
- Configure a 'strategy-type' to 'Rollingupdate' to trigger a rolling update when the deployment is updated.
- Add a 'spec-template.spec.imagePullPolicy: Always' to ensure that the new image is pulled even if it exists in the pod's local cache.

2. Create the Deployment: - Apply the updated YAML file using 'kubectl apply -f redis-deployment.yaml' 3. Verify the Deployment - Check the status of the deployment using 'kubectl get deployments redis-deployment' to confirm the rollout and updated replica count. 4. Trigger the Automatic Update. - Push a new image to the Docker Hub repository 5. Monitor the Deployment: - Use 'kubectl get pods -l app=rediS to monitor the pod updates during the rolling update process. You will observe that one new pod with the updated image is created, and then one old pod is terminated- This ensures that there is no downtime during the update process. 6. Check for Successful Update: - Once the deployment is complete, use 'kubectl describe deployment redis-deployment' to see that the 'updatedReplicaS field matches the 'replicas' field, indicating a successful update.

Correct Answer:

See the solution below with Step by Step Explanation.
Explanation:
Solution (Step by Step) :
1. Use a Deployment:
- Create a 'Deployment' object to manage your microservice.
- Specify the desired number of replicas and the container image.
- Use a 'rollinglJpdate' strategy to control the update process.

2. Control Rollout Pace: - Use the maxSurge' and 'maxlJnavailable' parameters to control the number of pods that can be unavailable or created during the update process. - For example, 'maxi-Inavailable: ensures that no pods are unavailable during tne update, while 'maxSurge: 1' allows for one extra pod to be created during the update. 3. Trigger Automatic Updates: - Use a 'Deployment's 'spec-template-spec-imagePullPolicy' to trigger updates automatically when a new image is available. - Set imagePullPolicy: Always' to force a pull of the image each time the deployment is updated. 4. Monitor Rollout Progress: - Use kubectl get pods -l app=my-microservice' to monitor the rollout progress. - You can also use tne 'kubectl rollout status deployment/my-microservice' command to get detailed information about the rollout. 5. Use Liveness and Readiness Probes: - Define liveness and readiness probes to ensure that containers are healthy and ready to serve traffic. - The 'Deployment' will automatically restart unhealthy containers, while readiness probes will ensure that new pods are only considered ready for traffic once they are healtny. 6. Traffic Routing: - Use a 'Service' to expose your 'Deployment' to external clients. - Configure the 'Service' to use a 'LoadBalancer' or 'NodePort' to make the service accessible from outside the cluster. Note: This approach ensures a smooth rollout with minimal downtime. New pods are created with the new image, and traffic is gradually shifted to the updated pods while the old pods are gracefully terminated. The liveness and readiness probes ensure that only healthy pods receive traffic, and the automatic updates triggered by 'imagePullPolicy: Always' keep the service up-to-date.

Correct Answer:

See the solution below with Step by Step Explanation.
Explanation:
Solution (Step by Step) :
I). Define the DaemonSet YAML: Create a YAML file that defines the DaemonSet configuration. This file will include the following key sections:
- Metadata Includes the name and labels for the DaemonSet.
- Spec: Defines the deployment details:
- Selector: Matches the labels of the pods that the DaemonSet should manage.
- Template: Contains the pod definition:
- Containers: Defines the main application container and the sidecar container.
- Ensure the sidecar container has appropriate resources and environment variables.
- Include any necessary ports or volume mounts for the sidecar container.
- UpdateStrategy: You might want to control the update strategy (RollingUpdate or Recreate) if you have multiple nodes.

2. Create the Daemonset Apply the Daemonset YAML file to your Kubernetes cluster using 'kubectl apply -f daemonset.yamr. This will create the DaemonSet and stan deploying tne pods on each node. 3. Verify Deployment: Use 'kubectl get daemonsetS to check the status of the DaemonSet. Verify that the pods are running on each node. 4. Testing and Monitoring: - Restart or Delete the Main App Pod: Observe how the sidecar container continues running alongside the main app pod, even when the main pod is restarted or deleted and recreated. - Check Logs If your sidecar container is responsible for logging, use 'kubectl logs to check the logs from the sidecar container This approach ensures that the sidecar container remains in a ready state on each node and is always available to support your application pod, fulfilling the requirements for logging and monitoring even when the main pod restarts or is recreated.

Correct Answer:

See the solution below with Step by Step Explanation.
Explanation:
Solution (Step by Step) :
1. Define Liveness Probe:
- Create a 'livenessProbe' within the 'containers' section of your 'web-app' Deployment YAML-
- Choose a probe type appropriate tor your application. In this case, since the startup is complex, use an 'exec' probe.
- Specify the command to execute. This should be a simple command that checks if the application is up and ready to handle requests.
- Set 'initialDelaySecondS and 'periodSeconds' to provide sufficient time for the application to start.
- Configure 'failureThreshold' and 'successThreshold' to define how many tailed or successful probes trigger a pod restart.

2. Define Readiness Probe: - Create a 'readinessProbe' Within the 'containers' section of your 'web-apps Deployment YAML. - Use the same 'exec' probe type as for the liveness probe. - Specify a command that checks it the application is ready to serve traffic. - Set 'initialDelaySeconds' and 'periodSeconds' to control the frequency and delay of the probe. - Configure 'failureThreshold' and 'successThreshold' to handle failed or successful probe results.

3. Deploy the Deployment: - Apply the updated YAML file using 'kubectl apply -f web-app.yamr 4. Verify the Probes: - Observe the pod logs using 'kubectl logs to see when liveness and readiness probes are executed. - Use 'kubectl get pods -I app=web-app' to check the status of pods and see how liveness and readiness probes affect the pod's health and availability. 5. Test the Application: - Send requests to the application to verify that it is healthy and responsive, even during startup. - Liveness Probe: The ' livenessProbe' checks if the application is still healthy and running. If the probe fails repeatedly, the Kubernetes will restart the pod to fix the issue. This ensures that unhealthy pods are removed and replaced with healthy ones. - Readiness Probe: The 'readinessproa' cnecks it the application iS ready to receive traffic. This allows Kubernetes to delay sending traffic to a pod until it is fully initialized and prepared to serve requests. It helps prevent users from encountering errors during startup. By using both liveness and readiness probes, you can ensure your application is healthy and available to users, even during complex startup sequences.,