define a component

• log on to the ocm-ui workspace in the konflux UI, created during onboarding, and under the ocm-ui application, add a new component.
• as per this guide, at this stage, use ./Dockerfile for the Dockerfile path, and select docker-build for the pipeline (the one without the oci-ta suffix).

set up access (not required when/if we have a public repo.)

add the required secrets for the component build.

according to konflux team, github repos with internal visibility (like ours), need to request access to be hosted on the internal cluster. the process is described in this doc. that's actually not true - see below.

private/internal github repos should use the public konflux cluster, but define a source-secret so the component is able to pull source-code from the repo.

(for GH repos,) this is done by adding a secret via the UI, with a secret-type "source secret".
(have a repo admin generate an ssh key and do this, or be granted temp' access in order to generate one).

update: apparently, we were hosted on the private konflux instance (is konflux.apps.stone-prod-p02.hjvn.p1.openshiftapps.com private?).
creating a source-secret might not even be necessary to fix the build errors – psturc@redhat.com -was able to create a new working component on the public instance.
once we get confirmation from the konflux-infra team (slack thread), the proposed course of action is to re-do the konflux-enablement from scratch, on the public instance (follow this guide).