Description of problem: An OpenShift admin can add a 3rd-party HelmChartRepository that requires specifying TLS client certificate and key. such HelmChartReposity CR looks like the following: apiVersion: helm.openshift.io/v1beta1 kind: HelmChartRepository metadata: name: sample-repo spec: connectionConfig: url: https://repo.foo.com tlsClientConfig: name: helm-tls-configs How reproducible: Deploy the above HelmChartRepo in the cluster and try to browse charts from UI Actual results: Content of default chart repository at https://github.com/redhat-developer/redhat-helm-charts is display, instead of the content of the custom chart repo. Expected results: Charts from the configured repo should be listed.
Created attachment 1717249 [details] Configuring Helm Chart Repo requiring TLS client certificates is working
Update from @spathak "I am able to create testing environment but still getting certificate issue which I'm working with app-services team to resolve it, I am successful in hosting helm with nginx but certificate mismatch is happening which I am trying to resolve"
Created attachment 1728307 [details] Configured Helm Chart Repo requiring TLS client certificates
Created attachment 1728308 [details] Configuring Helm Chart Repo requiring TLS client certificates is working
Verified on build version: 4.6.0-0.nightly-2020-11-07-035509 Browser version: chrome 84
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.6.4 bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:4987