Use case

As a cluster admin , I should be able to swap out Red Hat's helm chart repo with that of my own organization's helm chart repository. This will enable me to serve in-house helm charts, optionally in a disconnected environment.

Why

• Enterprises ( incl Red hat customers & IBM customers ) already have their own chart repositories which they prefer configuring for use with OCP. Given, Helm on OpenShift is GA in 4.4, the support for enterprise/air-gapped repositories is critical in 4.5
• Enterprises which run disconnected installs will be using the same mechanism to support helm charts in the Developer Catalog.

Goals

• Introduce a representation of a helm chart repository in the cluster, which users/admins should be able to create/read/update/delete
• The UI should let users do the above CRUD operations
• The "Developer Catalog" should show the helm charts from the configured helm chart repository.

How

• Introduce a new core API called HelmChartRepository
• Refactor console backend code to honor the presence of cluster-scoped HelmChartRepositories and render the Developer Catalog accordingly.