Onboard [PRODUCT NAME] to Konflux

Requestor: [your name/team]
Technical Contact: [email/slack]

Context

This ticket tracks onboarding [PRODUCT NAME] to Konflux. This involves creating a tenant workspace, configuring release pipelines, and setting up policy constraints.

Resources:

• Onboarding Guide: .cursor/rules/onboarding.mdc
• Konflux Onboarding Docs
• Need New Product ID?
• Creating Registry Repos (Comet)
• Creating Registry Repos (pyxis-repo-configs)

1. Product Information

(Requestor to complete)

Basic Product Details

• Product Name:
• Product ID (Engineering ID):
• Product Version (if applicable):
• Business Unit:
  • (_) Hybrid Platforms
  • (_) RHEL Platforms
  • (_) Application Developer
  • (_) Other: _______________
• Product Short Name (e.g., rhtap-qe):
  • This will be used for directory naming. The Konflux namespace will be [short-name]-tenant.

Source Code

• Git Repositories:
  • List all repositories and their default branches:
  • Example: https://github.com/org/repo (main)

Team Access

• GitLab Usernames:
  • Provide usernames for both Konflux workspace access (Admins) and GitOps repository permissions (CODEOWNERS).
  • Note: These are often the same people.
  • Admins: _______________
  • CODEOWNERS: _______________

Registry & Delivery

• Have you created delivery repositories in Pyxis?
  • (_) Yes, via Comet UI
  • (_) Yes, via releng/pyxis-repo-configs
  • (_) Not yet (Build team will assist)
• Registry URLs (if already created):
  • List all target registries (e.g., registry.redhat.io/my-prod/component1, registry.redhat.io/my-prod/component2):

Cluster Selection

• Do you already know which cluster you need?
  • (_) Yes → Cluster name: _______________
  • (_) No → Complete the questions below:

If you don't know your cluster, answer these:

• Do you need access to internal Red Hat RPMs or services? () Yes () No
• Is your repository hosted on internal GitLab? () Yes () No
• Are you building for public or internal Red Hat use? () Public () Internal
• Are you part of RHEL/OCP/OpenStack teams? () Yes () No (If yes, which: _______________)
• Any compliance or access restrictions? _______________

Release Configuration

• Environments needed:
  • (_) Staging only
  • (_) Production only
  • (_) Both Staging and Production
• Is this an Operator?
  • (_) Yes (requires FBC/Operator Catalog configuration with fbc-standard policy)
  • (_) No

2. Implementation Checklist

(Build Engineering Team)

• [ ] Determine cluster (if not provided by requestor)
• [ ] Create tenant workspace using tenants-config/add-namespace.sh
• [ ] Create ReleasePlanAdmission files (stage and prod)
• [ ] Create Constraint file to define allowed configurations
• [ ] Create FBC configuration (if product is an Operator)
• [ ] Assist with registry repository setup (if not already created in Pyxis)
• [ ] Update CODEOWNERS for self-service access
• [ ] Verify deployment in ArgoCD
• [ ] Handoff to product team:
  • Walk through configuration files
  • Explain how to make future updates
  • Verify first release runs successfully