Explanation:
To ensure the third-party logging solution runs on every node in the GKE cluster, a DaemonSet is the appropriate Kubernetes resource. DaemonSets guarantee that one pod of the specified application runs on each node automatically, making it ideal for node-level utilities like logging agents. Option B (modifying container images) would redundantly include the software in every pod, leading to inefficiency. Option C (manual SSH installation) is not scalable and violates GKE's managed node practices. Option D (Deployment) does not ensure one pod per node, as Deployments are designed for scaling across arbitrary nodes. Thus, the correct answer is A.
Ultimate access to all questions.
No comments yet.
To address intermittent performance issues in your GKE-deployed application, you need to install a third-party logging solution on every node in your cluster for log visibility. What steps should you take to accomplish this?
A
Deploy the third-party solution as a DaemonSet
B
Modify your container image to include the monitoring software
C
Use SSH to connect to the GKE node, and install the software manually
D
Deploy the third-party solution using Terraform and deploy the logging Pod as a Kubernetes Deployment