A development GKE container emitted excessive logs and increased costs. Disable those logs quickly with minimal steps. What should you do?

The correct option addresses the problem directly and efficiently. Disabling the log source for the specific GKE container resource in the Logs ingestion window of Stackdriver Logging (now Cloud Logging) will stop ingesting logs from that source, immediately reducing costs and log volume. The incorrect options are less efficient or incorrect. Disabling the log source for GKE Cluster Operations would affect all cluster logs, not just the problematic container. Deleting and recreating clusters is an extreme measure, causing downtime and significant operational overhead, and doesn't directly address log ingestion settings. "Legacy Stackdriver Logging" and "Legacy Stackdriver Monitoring" are outdated terms and don't offer the granular control needed to disable logs for a specific container.