A software engineering team is developing a containerized microservices application targeted for Google Kubernetes Engine (GKE). The team uses the browser-based Cloud Shell Editor and wants to accelerate their development inner loop. They have the following requirements: Automatically rebuild container images and redeploy workloads whenever source code files are modified and saved Automatically handle port forwarding and debugger argument injection into container runtimes Set breakpoints, inspect variables, and step through live execution against workloads running in a remote GKE development cluster directly from the IDE Which workflow and configuration should the team implement in Cloud Shell Editor?

Configure skaffold.yaml and a cloudcode.kubernetes launch configuration in launch.json, then run the Cloud Code: Debug on Kubernetes action with watch mode enabled: ### What Cloud Code Debug on Kubernetes Is **Cloud Code** in **Cloud Shell Editor** is an integrated extension that brings Google Cloud developer workflows directly into the browser-based IDE. Leveraging **Skaffold** (`skaffold debug`), Cloud Code provides a streamlined, continuous development workflow designed specifically for containerized workloads deployed to **Google Kubernetes Engine (GKE)**, local minikube, or Cloud Run. ### How It Meets the Requirements - **Continuous Build and Redeploy**: With the `watch` flag active in the `cloudcode.kubernetes` configuration, Cloud Code continuously detects local code modifications upon file save, automatically rebuilding container images via **Google Cloud Build** or local builders and redeploying manifests using **kubectl**. - **Automated Configuration and Port Forwarding**: Cloud Code powered by Skaffold automatically injects language-specific debugging arguments, rewrites entrypoints (e.g., Node.js inspect flags, Python `ptvsd`, Delve for Go, or Java JDWP agent options), and creates network port forwarding rules from the GKE pod to the Cloud Shell environment. - **Interactive In-IDE Debugging**: Developers can attach native IDE debuggers to live containers, set active breakpoints in the editor margin, inspect runtime variables, and step through code execution against the remote GKE cluster. ### Key Advantages and Capabilities - **Eliminates Manual Overhead**: Developers do not need to manually run `docker build`, tag images, push to **Artifact Registry**, update deployment manifests, or manually execute `kubectl port-forward`. - **Unified Configuration**: Integrates application orchestration via `skaffold.yaml` and editor launch behaviors via `.vscode/launch.json`. - **Automatic Resource Lifecycle Management**: When the debugging session terminates, Cloud Code automatically removes ephemeral Kubernetes development resources from the cluster. - **Multi-Module and Polyglot Support**: Allows independent development and debugging of separate microservices using modular Skaffold configurations across supported runtimes (Go, Python, Java, Node.js, .NET). ### Why This Is Optimal Using **Cloud Code: Debug on Kubernetes** provides full parity between the local development environment and cloud-hosted Kubernetes clusters while eliminating repetitive manual context switching, dramatically accelerating developer iteration cycles.

StudyCerts

Gke Cloud Code Debug Continuous Development | Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam! | StudyCerts

Professional Cloud Architect

Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam!

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Gke Cloud Code Debug Continuous Development

Section: Cloud Shell Editor, Cloud Code, and Cloud Shell Terminal

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

A software engineering team is developing a containerized microservices application targeted for Google Kubernetes Engine (GKE). The team uses the browser-based Cloud Shell Editor and wants to accelerate their development inner loop.

They have the following requirements:

Automatically rebuild container images and redeploy workloads whenever source code files are modified and saved
Automatically handle port forwarding and debugger argument injection into container runtimes
Set breakpoints, inspect variables, and step through live execution against workloads running in a remote GKE development cluster directly from the IDE

Which workflow and configuration should the team implement in Cloud Shell Editor?

Configure a continuous delivery pipeline in Google Cloud Deploy with Cloud Build triggers, and use Cloud Logging Logpoint injection to inspect remote execution

Use the Cloud Shell Terminal to execute skaffold dev, manually configure kubectl port-forward for language ports, and create a standard remote SSH launch configuration

Configure skaffold.yaml and a cloudcode.kubernetes launch configuration in launch.json, then run the Cloud Code: Debug on Kubernetes action with watch mode enabled

Execute gcloud builds submit on each code save and configure Cloud Profiler with Cloud Trace to capture execution stack traces from GKE workloads

Professional Cloud Architect

Gke Cloud Code Debug Continuous Development

Related questions