v1.14.0 Release Notes

Zadig v1.14.0 was released on August 18, 2022.

# Feature List

Workflow

• Product workflow supports configuring default branches
• Custom workflow supports common tasks
• Custom workflow supports selecting partial tasks for execution
• Custom workflow build tasks support configuring default branches
• Custom workflow supports using custom tasks
• Custom workflow supports global variables
• Custom workflow supports Git triggers
• Custom workflow supports MySQL tasks
• Support using variable $BRANCH to get code branch in Sonar code scanning

Environment

• Helm Chart projects and K8s YAML projects add dryRun operation before environment updates
• Environment supports change records
• K8s YAML projects support environment copying
• Support downloading files from containers

Others

• Managed projects support collaboration mode
• Developer center opens efficiency insights API
• Multi-cluster management supports kubeconfig method
• Zadig architecture optimization, component merging

Bugfix and Optimizations

• Fixed issue where workflow Webhook doesn't work when there are services with the same name in managed projects
• Fixed issue where custom workflow custom build image PATH is overwritten
• Fixed issue where custom workflow build tasks cannot pull custom build images
• Fixed issue where custom build variable values become invalid after variable name modification
• Fixed issue where extension steps are invalid in artifact workflows
• Fixed issue where clone directory is invalid in code scanning
• Support configuring common Git code sources in IP + PORT format

# Version Upgrade Process

# Database Backup

If already in production use, be sure to backup the database before upgrading

1. Database backup commands:

• Backup MongoDB data

mongodump -h IP --port PORT -u USERNAME -p PASSWORD -d DATABASE -o FILE_PATH

• 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

2. Database restore commands:

• Restore MongoDB data

mongorestore -h IP --port PORT -u USERNAME -p PASSWORD -d DATABASE --drop FILE_PATH

• 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

# 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 Kubernetes^New for upgrade.

# Installation Method: Helm Command Installation

For this installation method, execute the following steps to upgrade to v1.14.0:

1. 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

2. If you have previously modified the following values, please additionally modify the corresponding parameters

• microservice.user.database => connections.mysql.db.user
• microservice.config.dexdatabase => connections.mysql.db.dex

3. 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.14.0

• 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.14.0