Master Efficient Version Management and Release with Zadig’s Cloud‑Native Workflow
Zadig streamlines product delivery by offering a comprehensive version management and release process that guides engineers through creating versions, configuring environments, and executing production deployments for both K8s YAML and Helm Chart projects, enhancing transparency, control, and risk reduction.
In product delivery, version management and release are critical steps that affect quality and user experience. Effective version management helps teams organize and track code changes, while a well‑planned release process ensures new features go live smoothly with minimal risk. This article explains how to achieve efficient version management and release using the Zadig platform.
Core Delivery Process Overview
Engineers complete code development and deploy to the development environment for self‑testing and integration.
Submitted features undergo integration and system testing in the test environment to verify quality.
After all validations, the version is released to the production environment.
Typically, a test engineer confirms version validity and quality, packages the version, and hands it to a release engineer or R&D lead for production deployment.
The following sections detail how to create a complete version and perform a production release in Zadig’s K8s YAML and Helm Chart projects.
K8s YAML Project Release Scenario
Step 1: Create Version
Navigate to the K8s YAML project → Version Management → click Create Version to start the version‑creation workflow.
Fill in basic version information, including version name, tag, and description.
Select the target environment and service, then preview the configuration.
Choose the image repository and specify the required image version.
After confirming, the selected service image is pushed to the repository. In the version‑management list you can view detailed delivery information, including workflow tasks, image details, package data, service configuration, and startup order.
Step 2: Release Version
Execute the production release workflow. In the "Deploy" task select the created version, which updates all service images in the chosen environment. The workflow, pre‑configured by an administrator, typically includes Deploy, Test, and Manual Approval steps.
Helm Chart Project Release Scenario
Step 1: Create Version
Navigate to the Helm Chart project → Version Management → click Create Version .
Enter basic version details such as name, tag, and description.
Select environment and service, then make minor adjustments to meet production requirements.
If a global variable needs to be applied to all service values files, fill in the global variable and click Apply; all corresponding variables are updated automatically.
Choose the delivery repository, specify the Chart version, and configure the image version.
After completion, the selected Chart and image are pushed to the repository. Clicking the version shows details, including downloadable Chart information and image data.
Step 2: Release Version
Run the production release workflow. In the "Helm Chart Deploy" task select the version, which updates all Charts in the target environment. The workflow includes Helm Chart Deploy, Test, and Manual Approval steps.
Conclusion
Zadig provides an efficient solution for version management and release. By leveraging version creation and workflow‑based release features, teams gain greater transparency and control over the deployment process. Engineers can easily create versions, view detailed information, and execute releases, which improves efficiency, reduces risk, and ensures stable, high‑quality product delivery.
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.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.