You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
cozystack preset: custom registry mirrors via values #229
The preset hardcodes a single mirror (docker.io → https://mirror.gcr.io) in both the legacy registries.mirrors block and the multidoc RegistryMirrorConfig. Operators mirroring additional registries (e.g. ghcr.io), or pointing at a private pull-through cache with a custom TLS/insecure setting, must fork the preset.
Proposal
Expose the mirrors via values, driving both the legacy registries block and the RegistryMirrorConfig documents; keep the current gcr mirror as the default:
Should custom mirrors merge with the preset defaults or replace them entirely? Defining precedence for duplicate registries and whether authentication/TLS settings are supported alongside mirror endpoints would keep the values contract predictable for air-gapped installations.
Activity
hiSandog commentedon Jul 11, 2026
Should custom mirrors merge with the preset defaults or replace them entirely? Defining precedence for duplicate registries and whether authentication/TLS settings are supported alongside mirror endpoints would keep the values contract predictable for air-gapped installations.