Set up a component build in konflux:

• Create a downstream repo under https://gitlab.cee.redhat.com/istio/konflux . Some components can be built from the same repo, skip if a relevant repo already exists
  • Add the upstream repo as a submodule with the correct branch (consult upstream_source.yamls in current cpaas config)
  • Add a dockerfile to the repo (copy the component dockerfile from current cpaas config and tweak as necessary)
  • Create a token for the repo based on the instructions here
• Create the component in konflux tenants-config repo
  • copy one of the existing component manifests.
  • reference the downstream repo and its Dockerfile
  • if this component should be built for multiple architectures, make sure to put docker-build-multi-platform-oci-ta in the build.appstudio.openshift.io/pipeline annotation
  • submit a PR to the repo and ask someone on the team-ossm-konflux channel to approve it
• Wait for konflux to submit a PR with the build pipelines
  • after merging the konflux ui may still report it unmerged (this is a bug in the UI)
  • optional: refactor the generated files, extracting the pipelines from the pipelinerun (example PR). You can also change the pull-request pipeline to be single arch
• Make sure the build is passing
• Set up cachito configuration and enable hermetic build (docs, example PR)
• Resolve all issues reported for the component image in the enterprise-contract-stage integration test pipeline
• If this image should be referenced in the operator bundle image (i.e. this component is an operand), set up component nudging (docs)

Acceptance Criteria:

• component created in the service-mesh-tenant workspace in konflux
• component configuration set up using gitops in the tenants-config repo
• hermetic build enabled
• building on all architectures (if applicable)
• nudging the corresponding bundle (if applicable)
• passing Enterprise Contract