Answer-first summary for fast verification
Answer: Deploy the monitoring pod using a DaemonSet object.
The correct answer is **B** because a DaemonSet ensures that a copy of the monitoring pod is running on each node of the GKE cluster, making it the simplest and most efficient method to centralize monitoring. This approach automatically covers all nodes, including those added by auto-scaling, without requiring manual intervention or coordination among teams. - **A** is incorrect as it would necessitate manual configuration for each application, which is impractical and inefficient, especially with multiple teams involved. - **C** is incorrect because cluster initializers do not manage running pods; they customize cluster configurations during creation, and new nodes from auto-scaling would not have the monitoring pod by default. - **D** is incorrect because StatefulSets are designed for applications requiring stable network identities and persistent storage, not for deploying monitoring pods across all nodes. For further reading, consider this [article on K8s Deployments vs StatefulSets vs DaemonSets](https://medium.com/stakater/k8s-deployments-vs-statefulsets-vs-daemonsets-60582f0c62d4).
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
In a scenario where multiple teams deploy their applications on a single Google Kubernetes Engine (GKE) auto-scaling cluster, and you aim to centralize monitoring by running a monitoring pod that sends container metrics to a third-party monitoring solution, what is the simplest method to achieve this?
A
Request that developers include the monitoring pod in their deployments.
B
Deploy the monitoring pod using a DaemonSet object.
C
Initialize the cluster with the monitoring pod referenced at the time of GKE cluster creation.
D
Create a StatefulSet object for deploying the monitoring pod.
No comments yet.