Story (Required)

As a Konflux user, I would like to build the component through Konflux.

Background (Required)

- All the Red Hat products have to onboard on to Konflux by end of the year.

Out of scope

- Any other component

Approach (Required)

- Onboard the GitHub repo for the gitops-operator component on to the Konflux.
- Use one of the Docker build executors to get the component built.
- Modify the Dockerfile(if required) to make it more downstream.
      - Use a UBI image or Red Hat recommended Images for productization.
      - Use supported Red Hat versions of the packages (if required) for example Helm, Kustomize e.t.c.,.
      - Verify the built image is published to quay
      - Enable Hermetic build to ensure that the image can be built in disconnected environment.
      - Download the image from quay and test it locally.

Dependencies

<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>

Acceptance Criteria (Mandatory)

- Onboard the GitHub repo for the argo-cd component on to the Konflux.
- Use one of the Docker build executors to get the component built.
- Modify the Dockerfile(if required) to make it more downstream.
      - Use a UBI image or Red Hat recommended Images for productization.
      - Use supported Red Hat versions of the packages (if required) for example Helm, Kustomize e.t.c.,.
      - Verify the built image is published to quay
      - Enable Hermetic build to ensure that the image can be built in disconnected environment.
      - Download the image from quay and test it locally.

INVEST Checklist

Dependencies identified

Blockers noted and expected delivery timelines set

Design is implementable

Acceptance criteria agreed upon

Story estimated

Legend

Unknown

Verified

Unsatisfied

Done Checklist

• Code is completed, reviewed, documented and checked in
• Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
• Continuous Delivery pipeline(s) is able to proceed with new code included
• Customer facing documentation, API docs etc. are produced/updated, reviewed and published
• Acceptance criteria are met