Last month, your projects experienced higher-than-expected costs. After investigating, you discovered that a Google Kubernetes Engine (GKE) development container generated an excessive number of logs, contributing significantly to the increased expenses. You aim to swiftly disable these logs using the fewest possible steps. What actions should you take to achieve this?

Exam-Like

Go to the Logs ingestion window in Stackdriver Logging, and disable the log source for the GKE container resource.

68.3%

Go to the Logs ingestion window in Stackdriver Logging, and disable the log source for the GKE Cluster Operations resource.

16.8%

Go to the GKE console, and delete existing clusters. Recreate a new cluster. Clear the option to enable legacy Stackdriver Logging.

8.7%

Go to the GKE console, and delete existing clusters. Recreate a new cluster. Clear the option to enable legacy Stackdriver Monitoring.

6.2%

Google Associate Cloud Engineer