Explanation:
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.
For further reading, consider this article on K8s Deployments vs StatefulSets vs DaemonSets.
Ultimate access to all questions.
No comments yet.
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.