Quick note on adding mirror registry to Aliyun Kubernetes Container Services (ACK)
Briefly

Docker images pulling from docker.io is blocked in mainland China, necessitating the use of mirror registries. The author operates an Aliyun Kubernetes cluster on older versions and lacks SSH access, thus relying on scheduled jobs for configuration changes. Instead of creating two sets of configurations, the author aims to configure the existing Kubernetes setup to utilize mirror registries via containerd. This involves creating a hosts.toml file that directs image pulls while noting some unexpected behavior in the config.toml path after modifications.
To mitigate image pulling issues from docker.io in mainland China, I opted to configure containerd to use mirrors while maintaining a consistent Kubernetes setup.
By creating a hosts.toml file for docker.io, I can redirect image pulls to alternate registries without changing my core Kubernetes configurations.
Despite lacking SSH access to my Kubernetes cluster, I navigate configurations using scheduled jobs and command-line tools to keep my deployments streamlined.
The unexpected change to the config.toml path after adding hosts.toml highlights the intricacies of managing containerd and its configuration within a GFW environment.
Read at Medium
[
|
]