CI / CD with Container Registry — Part 2
2 min readJun 17, 2020
This is the last part from article “CI/CD with Container Registry”
Why Alibaba Cloud Container Registry?
Global Distribution
- 15 Region around the world
- Support pull image from VPC Intranet
Secure and Trust
Support Image Scan
Empower DevOps
- Built-in Support SCM (Github/Bitbucket/Gitlab)
- Integration with Container Service and Code Pipeline
Why Container Registry Service (ACR) Enterprise Edition?
Cloud-Native
- Dedicated registry instance with plug-in mechanism
- Manage Container images and Helm charts artifacts
- Downloading from VPC intranet
Security
- User-defined domain and network ACL
- Server-side encryption for storage
- Vulnerability scan and analysis
- Content trust (ongoing)
Large-scale Distribution
- P2P based image distribution
- Image Snapshot (ongoing)
Image Replication
- Policy based image replication across different regions
- Import images based on storage
- Image-syncer tool for Registry v2 based services
Security Pipeline
Global Distribution
- Globally distributed
- Low latency and high transfer speeds
Large-scale Distribution
- Large scale distribution in 10K nodes with P2P. Distribution efficiency improved 4-fold.
- Docker Image snapshot without pulling (ongoing).
Image Replication
- Global image replication between major regions. Replication efficiency improved 7-fold.
- Replicate images from other registries.
Sample CI / CD Pipeline on GitLab
This is the last part from article “CI/CD with Container Registry”
Part 1 — CI/CD Introduction
Part 2 — Container Registry: Enterprise Edition
Credit to: Alibaba Cloud