Story (Required)

See parent epic for high level details. GITOPS-5635 is a prerequisite for this story.

Also see resource links below for helpful external resources.

Sketch of work

(Continuing on from the build/release artifacts created in the openshift gitops operator Konflux workspace in GITOPS-5635)

1) Get hermetic build working

• Now that the build/release is working from previous story, the next step is enabling a hermetic build.
• Hermetic builds are requiring for releasing a Red Hat product.
• See https://konflux-ci.dev/docs/how-tos/configuring/hermetic-builds and https://konflux-ci.dev/docs/how-tos/configuring/prefetching-dependencies/

2) Move the work from your local GitHub repository to an official Red Hat repository that we can use for official builds

• In this previous story, I suggested that you create a Git repository  in your own organization, and create the Konflux Component from now.
• Now, we need to move/create a new repository in an official Red Hat org, for the official, proper builds.
• We need to find a place for that repo: 'redhat-developer' org or 'rh-gitops-midstream' org?
• My vote is 'rh-gitops-midstream'

3) Integrate your work with the existing 'openshift-gitops-operator' Application CR in Konflux workspace

• At present, we have an existing 'openshift-gitops-operator' Application in the 'rh-openshift-gitops' workspace.
• We should integrate the work of this JIRA with the existing OpenShift GitOps build
  • Argo Rollouts CLI would be a Component that points to the existing OpenShift GitOps Application

Acceptance Criteria

• New GitHub repository exists in redhat-developer or rh-gitops-midstream, containing Konflux artifacts, and that GitHub repository references Argo Rollouts via sub-module.
• Hermetic build of Rollouts kubectl plugin is enabled
• Konflux build from the above repository is building without any errors or warnings in Konflux UI.
• Rollouts CLI build is defined as a Component in 'rh-openshift-gitops' workspace, and is part of the 'openshift-gitops-operator' Application.

Resources

• #konflux-users slack channel: This is the 'customer support' mechanism for Konflux, where they have folks answering any/all Konflux questions. You can also use Slack search feature to search this channel, as your question may already have been answered.
• Konflux docs:
  • Internal docs: https://gitlab.cee.redhat.com/konflux/docs/users
  • External docs: https://konflux-ci.dev/docs/
• Examples of other team's Konflux configurations: https://gitlab.cee.redhat.com/releng/konflux-release-data/
  • You can find examples of other team's Konflux configurations within this repo.
  • For example, if you were looking for examples of 'ReleasePlanAdmission' object, you can clone the repo and run 'grep -r -i "kind: ReleasePlanAdmission"'
  • If you're looking for examples of other team's Pipelines, you can find other GitHub repositories that are onboarded onto Konflux by running 'grep -r -i "github.com"'.
• Other resource:
  • JIRA ticket which keeps track of which Konflux features we need for our migration to Konflux: https://issues.redhat.com/browse/KONFLUX-2308
  • See the other existing JIRAs we have for onboarding onto Konflux:
    • OpenShift GitOps Konflux Enablement: https://issues.redhat.com/browse/SECFLOWOTL-190
    • OpenShift GitOps Konflux Enablement: https://issues.redhat.com/browse/GITOPS-5018