Description

KLM needs to be configurable with a OCI repository sub-path. If the configured oci-registry-cred-secret is only containing the <registry-host>, KLM needs to be configurable with a <repository-sub-path> for the OCM lookup of modules.

Reasons

There were problems with KLM on a US pre-prod landscape. The operators transferred the kyma product into a registry with a repository sub-path, e.g. <registry-host>/<repository-sub-path>. KLM was configured with a oci-registry-cred-secret where only <registry-host> was given. This made KLM fail the OCM descriptor lookup because it was searching at <registry-host>/component-descriptors, not at <registry-host>/<repository-sub-path>/component-descriptors. According to SRE, the secret passed to oci-registry-cred-secret may be a more general secret to an OCI registry. It is a valid use case that this secret points to the <registry-host> only where it is necessary that KLM is configured additionally with the sub-path in this registry where the module OCMs are stored.

Acceptance Criteria

• OCI registry host and sub path configurable independent of each other
• No flag name change