Skip to content

How to pull operator containers from a private/custom registry #1417

@chris-rock

Description

@chris-rock

Question: Fetching Operator Containers from a Private Registry

Requirement

The user wants to configure the k8s operator to fetch its containers from their own registry (e.g., a private mirror or air-gapped environment), rather than the default public source.

Questions

  • Do we have existing documentation covering this use case?
  • If not, should we add a guide or section to the operator docs explaining how to configure a custom/private registry?

Proposed Action

  • Check whether this is documented anywhere (docs site, README, Helm chart values, etc.)
  • If undocumented, create a doc or add a section covering the steps to configure a private registry for operator containers
  • Optionally, link this from the operator's FAQ or troubleshooting guide

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions