You have an application that runs in Google Kubernetes Engine (GKE)
Over the last 2 weeks, customers have reported that a specific part of the application returns errors very frequently.
You currently have no logging or monitoring solution enabled on your GKE cluster.
You want to diagnose the problem, but you have not been able to replicate the issue.
You want to cause minimal disruption to the application.
What should you do?
Click on the arrows to vote for the correct answer
A. B. C. D. E.C.
https://cloud.google.com/blog/products/management-tools/using-logging-your-apps-running-kubernetes-engineThe best option in this scenario would be to start with option A: Update your GKE cluster to use Cloud Operations for GKE.
Cloud Operations for GKE is a logging and monitoring solution that is integrated with GKE. It provides access to logs and metrics for your GKE clusters, nodes, and workloads. It also includes pre-built dashboards that allow you to monitor the health and performance of your GKE workloads.
By enabling Cloud Operations for GKE, you can start collecting logs and metrics for your application, which will allow you to investigate the reported errors. You can use the GKE Monitoring dashboard to investigate logs from affected Pods and identify the root cause of the problem.
It is important to note that enabling Cloud Operations for GKE does not require any changes to your application or cluster configuration. It also does not require any downtime or disruption to your application.
Options C and E suggest creating a new GKE cluster with Cloud Operations for GKE enabled and migrating the affected Pods to the new cluster. While this is a possible solution, it is more complex and requires additional configuration and testing. It also involves redirecting traffic to the new cluster, which can cause disruption to your application.
Option D suggests updating your GKE cluster to use Cloud Operations for GKE and deploying Prometheus to set an alert to trigger whenever the application returns an error. While this is a valid option, it requires more configuration and management of Prometheus, which may not be necessary for this scenario.
In summary, the best option in this scenario is to enable Cloud Operations for GKE and use the GKE Monitoring dashboard to investigate logs from affected Pods. This approach minimizes disruption to your application and provides a quick and easy solution for diagnosing the reported errors.