Owner: Architect:

Story (Required)

As an OpenShift user, I want to be able to use helm features on a multi cluster aware OCP console.

Background (Required)

OCP Console is going to support multi cluster environment from 4.9. This multi cluster aware environment has a hub cluster running the OCP console which connects to multiple spoke clusters. We need to now check the list of proxy config available to obtain api url and certs for the target OpenShift cluster. The cluster name will come as part of the request header (X-CLUSTER).

Glossary

N/A

Out of scope

N/A

In Scope

Test in a single cluster setup, no regressions.
Test in a multi-cluster setup.

Approach(Required)

We will depend on this PR: https://github.com/openshift/console/pull/9561

We can use this utils function to parse the header out of the request: https://github.com/openshift/console/pull/9561/files#diff-18fa81be5d4e502ba1f45bb0d1dfe857e7fba9e884b1750640100ab10b3b88efR11

Then change this method to use the new proxy info mapped to cluster name: https://github.com/openshift/console/pull/9561/files#diff-18fa81be5d4e502ba1f45bb0d1dfe857e7fba9e884b1750640100ab10b3b88efR11

The new proxy info will be available in this map: https://github.com/openshift/console/pull/9561/files#diff-a6a05e882aef5d5df310ac3ef6a9aba95fc7f54471fd43c661d528c09c7263efR246

Dependencies

We will need this merged first: https://github.com/openshift/console/pull/9561

Edge Case

N/A

Acceptance Criteria

1. Can still connect to local cluster when no header provided.
2. Can create a helm release in a remote cluster when header is provided.

INVEST Checklist

Dependencies identified
Blockers noted and expected delivery timelines set
Design is implementable
Acceptance criteria agreed upon
Story estimated

Legend

Unknown
Verified
Unsatisfied