How Lixun Logistics Cut Registry Complexity by 50% with Alibaba Cloud ACR EE
Facing high operational costs and scaling challenges with its self-built Harbor registry, Lixun Logistics migrated core container images to Alibaba Cloud’s ACR Enterprise Edition, achieving a 50% reduction in registry complexity, 60% faster image distribution, and enhanced security across multi-region deployments.
Background and Migration Motivation
In 2021 Lixun Logistics began moving its container‑image registry from an on‑premise Harbor instance to Alibaba Cloud Container Registry Enterprise Edition (ACR EE) to support a large‑scale, multi‑region cloud‑native deployment. The on‑premise solution required extensive effort to achieve high availability, bandwidth, and security, and its image‑version management could not keep pace with rapid business growth.
Target Architecture
All core container images and Helm charts were migrated to ACR EE and used together with Alibaba Cloud Container Service for Kubernetes (ACK) as the unified image‑management and scheduling platform.
Key Technical Benefits of ACR EE
Enterprise‑grade image and Helm chart hosting with built‑in vulnerability scanning, encryption, and signing.
Unlimited, highly durable storage that eliminates capacity‑planning for image repositories.
High‑throughput concurrent pulls and multi‑region synchronized replication.
Custom domain support via PrivateZone, enabling a single DNS name across regions and hybrid‑cloud environments.
99.95% SLA and P2P acceleration for large‑scale image distribution.
Automatic image cleanup and version‑retention policies that prevent repository bloat.
Migration Procedure
Enable the Image Import feature in the ACR EE console.
Specify the source Harbor registry URL and credentials; ACR EE pulls all repositories and tags automatically.
Configure a custom domain on the ACR EE instance and bind the same DNS records used by the original Harbor service, ensuring seamless client compatibility.
Validate image integrity with ACR EE’s built‑in checksum verification and security scanning.
Update Kubernetes imagePullSecrets and deployment manifests to reference the new ACR EE repository URL.
The entire import process completed in approximately one hour, with no manual image re‑tagging required.
Post‑Migration Outcomes
Operational cost for the container registry decreased by ~50% due to the elimination of self‑managed Harbor infrastructure.
Image distribution latency improved, yielding a ~60% increase in pull throughput across all regions.
Version management became fully automated; weekly retention policies removed tens of thousands of stale image tags without impacting active workloads.
End‑to‑end security was enforced through automatic vulnerability scanning, image signing, and encrypted storage.
Integration with Alibaba Cloud Ecosystem
ACR EE integrates natively with ACK, Cloud Effect pipelines, and other Alibaba Cloud services, providing a continuous integration/continuous delivery (CI/CD) workflow that includes:
Automated image build and push from CI pipelines.
Security scanning as a gate before promotion to production namespaces.
Version‑controlled Helm chart repositories for Kubernetes deployments.
This integration enables a full‑chain DevSecOps process, allowing Lixun Logistics to deliver business services rapidly while maintaining strict security and compliance controls.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
Alibaba Cloud Native
We publish cloud-native tech news, curate in-depth content, host regular events and live streams, and share Alibaba product and user case studies. Join us to explore and share the cloud-native insights you need.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
