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
Support private OCI registry credentials for platform source #2455
Currently, the cozystack-operator creates the OCIRepository Flux resource via --platform-source-url but has no way to attach registry credentials. This makes it impossible to use a private OCI registry (e.g. GitLab Container Registry) as the platform source.
The OCIRepository CRD supports spec.secretRef pointing to a kubernetes.io/dockerconfigjson secret, but the operator's generateOCIRepository() function does not populate this field, and there is no corresponding flag to configure it.
Additionally, because the operator does a full Update() of the OCIRepository spec on every restart, any manually applied patch with secretRef gets overwritten.
Proposed Solution
Add a --platform-source-secret flag to the operator that accepts the name of a Secret in the cozy-system namespace containing the registry credentials. This secret name would then be set as spec.secretRef in the generated OCIRepository (and GitRepository for private Git sources).
The installer Helm chart (packages/core/installer) would expose a corresponding cozystackOperator.platformSourceSecret value.
Activity
overhovnik commentedon Jun 2, 2026
Hey,
i really appreciate that you already prepared everything for the change.
Is there any schedule when this will/could be merged?
Thanks and greetings
Oliver
feat(operator): support private OCI registry credentials for platform…
feat(operator): support private OCI registry credentials for platform…