Administrator Manual
# Overview
This manual is written for Zadig administrators and can help you quickly manage and configure the Zadig system (such as: code source integration, account system access, image repository/object storage/Helm Chart repository/cluster management, etc.).
# Third-Party System Integration
| System | Description | Configuration Method |
|---|---|---|
| Account System | Access to the Unified Account System within the Enterprise | LDAP OAuth 2.0 DingTalk Feishu WeChat Work |
| Code Repository | Integration of the code repository used by the enterprise | Code Source Integration |
| Project Management | Integration of the project management platform to automatically change the status of workflow tasks | Jira Integration Feishu Project Integration |
| Configuration Management | Integration of configuration management tools to automatically change business configurations in workflows (Apollo configuration/Nacos configuration) | Apollo Configuration Nacos Configuration |
| Code scanning | Integration of the Sonar system for Sonar code scanning | Sonar Integration |
| Approval System | Integration of the approval system for workflow process approval | Approval System Integration |
# Infrastructure Management
| System | Description | Configuration Method |
|---|---|---|
| Image Repositories | Integration of the image repository used in the project | Image Repository |
| Object Storage | Integration of object storage for storing workflow history logs, test reports, and build caches | Object Storage |
| Helm Chart Repositories | Integration of the Helm Chart repository for pulling and pushing Chart services | Helm Repository |
| Cluster Management | Multi-cluster management for workflow task execution and service deployment | Cluster Management |
# Advanced Usage
# Increase the Available Disk Space of the System
When the workflow execution fails due to insufficient disk space, the disk space used by the Zadig system needs to be increased. This can be addressed from two perspectives: releasing disk space and increasing disk space.
- Releasing Disk Space: Access system settings -> Settings -> Cache Cleaning -> One-click cleanup to quickly release disk space.
Tip
To avoid the cache resources generated by the system's long-term operation of the system to occupy disk space, you can set a regular cleaning. See cache cleaning. Note: After cleaning the image cache, the efficiency of the initial workflow to build the image may be affected. Please confirm that it is correct before operating.
- Increase disk space: Access Resourcing -> Cluster Management -> cluster, modify Dind resource configuration, adjust storage space size, see Dind Resource configuration.
# Workflow Build Efficiency Optimization
Tip
Optimize the execution efficiency of workflow builds from the perspectives of workflow configuration and cluster resource configuration. The following methods can all improve workflow execution efficiency:
- Enable build caching to save build execution time
- Use higher-spec build resources
- Configure workflow concurrent execution
- Use PVC resources as cache storage media
- Use higher-configured Dind resources
Enabling Build Caching
Go to the project -> Build -> Advanced Configuration, enable cache configuration and customize the cache directory. See Workflow Build Cache.
Build Resource Configuration
Visit the project -> Build -> Advanced Configuration, select a higher-spec operating system configuration, see Build Advanced Configuration.
Enabling Workflow Concurrent Execution
- Access system settings -> System configuration -> task configuration, set the number of task concurrency, see task configuration.
- Edit workflow -> Turn on concurrent execution, see Workflow runs concurrently.
Setting Cluster Cache Resource Configuration
Access Resourcing -> Cluster Management-> Edit the cache resource configuration of the cluster, see cache resource configuration.
Setting Cluster Dind Resource Configuration
Access Resourcing -> Cluster Management-> Edit cluster's Dind resource configuration, see Dind resource configuration.
# Configuring Task Scheduling Resources
Set the cluster's scheduling policy to schedule tasks to run on specified nodes, ensuring efficient resource usage.
Access Resourcing -> Cluster Management -> Edit the scheduling policy of the cluster, see Scheduling policy configuration.
Scenario 1: All available nodes in the cluster can be used to run tasks, choose random scheduling. Scenario 2: Only tasks are allowed to run on specified nodes, add a dedicated label to the nodes, and choose forced scheduling. Scenario 3: All available nodes in the cluster can be used to run tasks, but you want to prioritize certain nodes, add labels to the nodes, and choose priority scheduling. Scenario 4: To achieve finer-grained resource scheduling, add taints to nodes and configure tolerations in the scheduling policy.
# Multi-Cluster Resource Management
To achieve fine-grained cluster resource management, such as different teams' projects using different cluster resources.
Access Resourcing -> Cluster Management -> Add cluster. See Cluster Management. For different network situations, use different methods to access the cluster:
- External clusters that can access the cluster where Zadig is located can use a proxy connection.
- The cluster where Zadig is located can access external clusters and use a direct connection.
