Registry Mirroring and Caching Decision Tree

Registry Mirroring and Caching Decision Tree A workflow diagram generated by Archify. 01 / Identify the problem 02 / Rate limit issues · your environment 03 / Rate limit strategies 04 / Availability/Performance · infrastructure 05 / Availability/Performance strategies Diagnose Choose a strategy Cache or mirror needed? · what is the problem? · Identify the problem › Diagnose Cache or mirror needed? what is the problem? Your environment · where do you run? · Rate limit issues · your environment › Diagnose Your environment where do you run? ECR Pull-through Cache · pull-through-cache-rule · Rate limit strategies › Choose a strategy ECR Pull-through Cache pull-through-cache-rule Harbor Proxy Cache · Proxy Cache project · Rate limit strategies › Choose a strategy Harbor Proxy Cache Proxy Cache project containerd mirror config · config.toml mirrors · Rate limit strategies › Choose a strategy containerd mirror config config.toml mirrors Infrastructure · what does it look like? · Availability/Performance · infrastructure › Diagnose Infrastructure what does it look like? Harbor full mirror · disconnected environment · Availability/Performance strategies › Choose a strategy Harbor full mirror disconnected environment ECR Replication · cross-region replication · Availability/Performance strategies › Choose a strategy ECR Replication cross-region replication Harbor Pull Replication · pull to edge sites · Availability/Performance strategies › Choose a strategy Harbor Pull Replication pull to edge sites Availability/Performance Rate limit issues Multi-region Air-gap Edge Simple mirror AWS/EKS Self-hosted Legend Decision step AWS managed (ECR) Self-hosted (Harbor / containerd)