v1.13.0 Release Notes

Zadig v1.13.0 was released on July 8, 2022.

# Feature List

Features

• Support custom orchestrable workflows
• Support project-level host management
• Service detail information adds node information and Pod Ready status
• Environment-Service view supports launching debug containers
• Support Dind disk mounting
• Environment configuration supports automatic synchronization

Bugfix and Optimizations

• Optimize workflow list page loading efficiency
• Optimize version management status display, support image filtering
• Optimize resource deletion logic after deleting service definitions and updating environments
• Fixed issue where code repository information cannot be searched when using build templates
• Fixed issue where JIRA information cannot be retrieved in branch build scenarios
• Fixed issue where artifact deployment workflow clone tasks cannot get image information
• Provide error prompt when creating services with duplicate names
• Fixed issue where GitHub code repository selection doesn't filter by organization/user
• Fixed workflow-related issues when image names contain underscores
• Fixed automatic retry issue after test task timeout
• Fixed issue where workflow task status becomes timeout after cancellation
• Fixed environment configuration related issues
• Fixed branch selection issue for "Other" type code scanning
• Fixed page error after deleting all services in Helm Chart environment
• Fixed hub-agent excessive connection issue

# 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.13.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. 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.13.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.13.0