Exam KCNA topic 1 question 49 discussion

In summary, both commands "kubectl rollout status" and "kubectl rollout watch" provide a real-time feedback on rollout progress but "kubectl rollout watch" continuously watches until completion while "kubectl rollout status" provides a snapshot of the current status.

D

❯ kubectl rollout watch error: unknown command "watch" Available Commands: history View rollout history pause Mark the provided resource as paused restart Restart a resource resume Resume a paused resource status Show the status of the rollout undo Undo a previous rollout --> So answer is D

D is correct answer

kubectl rollout watch Purpose: This command is not a standard kubectl command. It seems like a misunderstanding or a mix-up with kubectl get events --watch or similar commands that watch for changes in resources. Behavior: If you meant kubectl get events --watch, it watches for changes in events related to the resources in the cluster, providing real-time updates. Answer: D

D. is correct "kubectl rollout status"

D. kubectl rollout status Correct. kubectl rollout watch is not a valid Kubernetes command.

The correct answer to the question "How can you monitor the progress for an updated Deployment/DaemonSets/StatefulSets?" is D. kubectl rollout status. Explanation: The kubectl rollout status command is used to monitor the progress of a rollout for Kubernetes resources such as Deployments, DaemonSets, or StatefulSets. This command provides real-time updates on whether the new Pods are being created correctly and whether the old ones are being terminated. It ensures that the rollout is proceeding as expected and alerts if any issues occur during the update. Other options like kubectl rollout watch, kubectl rollout progress, and kubectl rollout state are not valid Kubernetes commands for monitoring rollout progress. The proper command to use for tracking progress is kubectl rollout status

Option A (kubectl rollout watch) is not the correct choice because the kubectl rollout watch command is used to continuously monitor the rollout progress of a deployment, allowing you to watch for changes in the rollout status in real-time. However, it is specifically designed for monitoring deployments and does not directly apply to DaemonSets or StatefulSets. While you could use kubectl rollout watch for deployments, it may not provide accurate or relevant information for DaemonSets or StatefulSets. Therefore, option A is not the most suitable command for monitoring the progress of updates to DaemonSets or StatefulSets. On the other hand, option D (kubectl rollout status) is a more generic command that works for all types of rollouts, including deployments, DaemonSets, and StatefulSets. It provides detailed information about the status of the rollout, making it a better choice for monitoring the progress of updates across different types of workload controllers in Kubernetes.