v1.11.0 Release Notes
Zadig v1.11.0 was released on April 21, 2022.
# Feature List
Project
- Support Helm version management retag image
- Support Helm Chart template library import from Gerrit code source
- Support Helm Chart import from Microsoft Azure, Alibaba Cloud ACR repositories
- Support custom Helm Release names
- Support independent management of Pod Debug permissions
Environment
- K8s YAML project environments support enabling self-test mode
- K8s YAML project environment creation supports selecting partial services
- K8s Helm Chart project environment creation supports selecting partial services
- Environment configuration supports Ingress/ConfigMap/Secret/PVC resource types
- Service deployment supports inconsistent image names and service container names
- Host environments support login debugging
Workflow
- Workflow supports distribution deployment steps
- Jenkins build execution parameters support IMAGE variable rules & Choice parameter types
- Build supports uploading specified files to S3 object storage
System Settings
- Code source supports Gitee integration
- Sensitive information encrypted processing
- Support image registry configuration with self-signed certificates
- Image cache supports scheduled cleanup
- Infrastructure compatible with Kubernetes 1.22 version
- PVC cache supports custom cache directories
- Host management adds host status display
Feature Optimization
- Workflow task execution supports selecting TAG without configuring "Distribution" step
- Multiple service component updates in the same Helm Chart require only one deployment
- Workflow extension step request parameters enhanced
- Host project build scripts support environment variables for host information, environment information, etc.
- K8s YAML project environment variable updates support variable search
- Image names support using first eight characters of Commit ID generation rule
Bugfix
- Fixed service update failure triggered by Webhook when configuring multiple GitLabs with same address
- Fixed build Job not being cleaned up in time after build timeout
- Fixed workflow timer quick toggle being ineffective
- Fixed slow environment loading when Ingress resources exist
- Fixed newly created services in host projects not syncing to environments
- Fixed collaboration mode related issues
# Version Upgrade Process
Warning
If current system version < v1.10.0, please first upgrade to v1.10.0. For specific upgrade process, see v1.10.0 Upgrade Method, then follow the method below to upgrade to v1.11.0
# Database Backup
If already in production use, be sure to backup the database before upgrading
- Database backup commands:
- Backup MongoDB data
mongodump -h IP --port PORT -u USERNAME -p PASSWORD -d DATABASE -o FILE_PATH
1
- Backup MySQL data
mysqldump -h <HOST> -P <PORT> -u root -p user > user.sql
mysqldump -h <HOST> -P <PORT> -u root -p dex > dex.sql
1
2
2
- Database restore commands:
- Restore MongoDB data
mongorestore -h IP --port PORT -u USERNAME -p PASSWORD -d DATABASE --drop FILE_PATH
1
- Restore MySQL data
# Execute the following in MySQL:
mysql> drop database user;
mysql> create database user;
mysql> drop database dex;
mysql> create database dex;
# Execute the following data recovery operations from command line:
mysql -h <HOST> -P <PORT> -u root -p user < user.sql
mysql -h <HOST> -P <PORT> -u root -p dex < dex.sql
1
2
3
4
5
6
7
8
2
3
4
5
6
7
8
# Upgrade Operations
Please execute corresponding upgrade steps according to different installation methods.
# Installation Method: All in One Installation Mode or Installation on Existing Kubernetes
For both installation methods, use scripts from Installation on Existing KubernetesNew for upgrade.
# Installation Method: Helm Command Installation
For this installation method, execute the following steps to upgrade to v1.11.0:
- Execute the following command and check the zadig.yaml file. If the file contains image information (i.e.,
tag:a.b.c), it needs to be manually deleted.
helm get values <Release Name> -n <Zadig Namespace> > zadig.yaml
1
- Execute upgrade command according to installation method.
- Domain method:
export NAMESPACE=<Zadig Installation NAMESPACE>
helm repo update
helm upgrade -f zadig.yaml <release_name> koderover-chart/zadig --namespace ${NAMESPACE} --version=1.11.0
1
2
3
4
2
3
4
- IP + PORT method:
export NAMESPACE=<Zadig Installation NAMESPACE>
export PORT=<Any port between 30000-32767, different from initially used port>
helm repo update
helm upgrade -f zadig.yaml <release_name> koderover-chart/zadig --namespace ${NAMESPACE} \
--set gloo.gatewayProxies.gatewayProxy.service.httpNodePort=${PORT} \
--set gloo.gatewayProxies.gatewayProxy.service.type=NodePort --version=1.11.0
1
2
3
4
5
6
7
2
3
4
5
6
7
Post-Upgrade Considerations
- If upgrading from v1.10.0 to v1.11.0 and external clusters were integrated in the Zadig system before upgrade, after upgrading to v1.11.0, you need to disconnect the external cluster connection and re-integrate it, otherwise the functionality of using that cluster for builds will be abnormal. For cluster integration, refer to: Cluster Management.


