Operations 6 min read

Master Remote Debugging and Service Management with Zadig Toolkit in VS Code

Zadig Toolkit, a VS Code extension from KodeRover, lets developers view and manage Zadig environments, restart services, switch images, debug remotely, and sync code without committing or building images, providing step‑by‑step guidance on installation, configuration, remote debugging, and service inspection.

Ops Development Stories
Ops Development Stories
Ops Development Stories
Master Remote Debugging and Service Management with Zadig Toolkit in VS Code

Zadig Toolkit is a Visual Studio Code plugin from KodeRover that provides core Zadig capabilities directly in the IDE, allowing developers to view and manage environments, restart services, switch images, view logs, and perform remote debugging without committing code or building images.

Preparation

System: Install Zadig v1.12.0.

Project: Follow Zadig official tutorial for GitHub + Zadig continuous delivery.

Install Plugin

Open VS Code and go to the Marketplace.

Search for "Zadig Toolkit", view details and install.

Configure Plugin

Open the installed Zadig Toolkit plugin.

Click "Settings" to open the configuration page.

Configuration parameters:

Zadig deployment address (e.g., http://zadig.com).

Zadig API Token: obtain from Zadig system → Account Settings.

How to Use

Remote Debug Local Code

Using the

voting-demo

project as an example, the steps are:

Select the

voting-demo

project →

dev

environment, set Kube Config, press Enter.

Select the

vote

service and click the debug button to enter development mode.

Choose the local source directory (e.g.,

koderover/zadig/examples/voting-app

).

Select the base image, e.g.,

python:3.10.4-buster

.

After the development container starts, modify code (e.g., change button color); changes sync automatically.

Run the following commands inside the dev container:

<code>pip install -r requirements.txt -i https://mirrors.aliyun.com/pypi/simple/

gunicorn app:app -b 0.0.0.0:80 --log-file - --access-logfile - --workers 4 --keep-alive 0</code>

Access the service URL to see the updated UI.

View Environment and Service

In the left sidebar you can see projects, view service status, restart services, replace images, view real‑time logs, or open a terminal to the pod.

Right‑click a service → "Restart Service".

Right‑click a service → "Terminal" to log into the pod.

Configure Remote Development Environment

Modify the base image or code directory via the "Development Mode Configuration" button.

Configuration fields: projectName, envName, serviceName, containerName, image, codeDir.
<code>[
  {
    "projectName": "project name",
    "envName": "environment name",
    "serviceName": "service name",
    "containerName": "development container name",
    "image": "base image",
    "codeDir": "local directory to sync"
  }
]</code>

After saving, click "Start Development Mode" to launch.

Overall, Zadig Toolkit streamlines cloud service management and remote debugging directly from VS Code.

Cloud NativeKubernetesDevOpsremote debuggingVS CodeZadig
Ops Development Stories
Written by

Ops Development Stories

Maintained by a like‑minded team, covering both operations and development. Topics span Linux ops, DevOps toolchain, Kubernetes containerization, monitoring, log collection, network security, and Python or Go development. Team members: Qiao Ke, wanger, Dong Ge, Su Xin, Hua Zai, Zheng Ge, Teacher Xia.

0 followers
Reader feedback

How this landed with the community

login Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.