Skip to content

feat: BYO container registry support#98

Open
minmzzhang wants to merge 1 commit intovalidatedpatterns:mainfrom
minmzzhang:byo-container-registry-fresh-install
Open

feat: BYO container registry support#98
minmzzhang wants to merge 1 commit intovalidatedpatterns:mainfrom
minmzzhang:byo-container-registry-fresh-install

Conversation

@minmzzhang
Copy link
Collaborator

Restructure registry configuration to support three deployment states:

  • Fresh install: No registry configured (both disabled by default)
  • Built-in Quay: quay.enabled=true uses hub/infra/quay/ vault path
  • External/BYO: externalRegistry.enabled=true uses hub/infra/registry/ path

Changes:

  • Add externalRegistry.enabled flag to supply-chain and qtodo charts
  • Separate vault paths for built-in Quay vs external registry
  • Templates conditionally select vault path based on enabled flags
  • Update supply-chain.md with BYO registry setup instructions
  • Add helm template method and oc monitoring commands to supply-chain.md
  • Follow VP best practice: external registry secrets in local ~/values-secret.yaml

To enable supply-chain:

  1. Uncomment openshift-pipelines namespace and subscription
  2. Uncomment supply-chain vault role (JWT auth)
  3. Configure registry (BYO or built-in Quay) in application overrides
    • For BYO registry:
      • Set externalRegistry.enabled=true and configure registry settings
      • Add registry credentials to ~/values-secret.yaml
    • For built-in Quay:
      • Enable openshift-storage namespace
      • Enable ODF, NooBaa MCG
      • Enable Quay operator subscription, quay-registry application
  4. RHTAS (signing): Enable rhtas-operator subscription and trusted-artifact-signer namespace
  5. RHTPA (SBOM): Enable rhtpa-operator subscription, ODF, NooBaa, and trusted-profile-analyzer

Signed-off-by: Min Zhang minzhang@redhat.com

@mlorenzofr mlorenzofr self-requested a review February 10, 2026 08:59
@minmzzhang minmzzhang force-pushed the byo-container-registry-fresh-install branch 2 times, most recently from 1dc6409 to 8a6e153 Compare February 11, 2026 20:19
Restructure registry configuration to support three deployment states:
- Fresh install: No registry configured (both disabled by default)
- Built-in Quay: quay.enabled=true uses hub/infra/quay/ vault path
- External/BYO: externalRegistry.enabled=true uses hub/infra/registry/ path

Changes:
- Add externalRegistry.enabled flag to supply-chain and qtodo charts
- Separate vault paths for built-in Quay vs external registry
- Templates conditionally select vault path based on enabled flags
- Update supply-chain.md with BYO registry setup instructions
- Add helm template method and oc monitoring commands to supply-chain.md
- Follow VP best practice: external registry secrets in local ~/values-secret.yaml

To enable supply-chain:
1. Uncomment openshift-pipelines namespace and subscription
2. Uncomment supply-chain vault role (JWT auth)
3. Configure registry (BYO or built-in Quay) in application overrides
   - For BYO registry:
     - Set externalRegistry.enabled=true and configure registry settings
     - Add registry credentials to ~/values-secret.yaml
   - For built-in Quay:
     - Enable openshift-storage namespace
     - Enable ODF, NooBaa MCG
     - Enable Quay operator subscription, quay-registry application
4. RHTAS (signing): Enable rhtas-operator subscription and trusted-artifact-signer namespace
5. RHTPA (SBOM): Enable rhtpa-operator subscription, ODF, NooBaa, and trusted-profile-analyzer

Signed-off-by: Min Zhang <minzhang@redhat.com>
@minmzzhang minmzzhang force-pushed the byo-container-registry-fresh-install branch from 8a6e153 to 9274825 Compare February 11, 2026 22:08
Copy link
Collaborator

@mlorenzofr mlorenzofr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It works with all three options provided.

Perhaps it could have been developed with a more general approach, instead of being case-specific, but that's just my personal opinion.

LGTM

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants