Skip to content

cozystack preset: custom registry mirrors via values #229

Open

Description

Problem

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:

registryMirrors:
  docker.io: { endpoints: [https://registry.example.com/v2/docker.io] }
  ghcr.io:   { endpoints: [https://registry.example.com/v2/ghcr.io], insecureSkipVerify: true }

Activity

  1. hiSandog commented on Jul 11, 2026

    @hiSandog

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions