Epic Goal

• Enhance the cluster-proxy-addon to be able to proxy to any service on a managed cluster

Community issue:

https://github.com/open-cluster-management-io/cluster-proxy/issues/53 

Why is this important?

• Currently the cluster-proxy only supports the cluster's api server as an endpoint
• Some customers and internal stakeholders have use cases to be able to reach directly into the managed cluster from the hub to interact with some services

Scenarios

1. A service or user can apply configuration the cluster-proxy to enable it to reach a given service in a cluster or multiple clusters
2. A service or a user can then make a request to the cluster proxy endpoint on the hub cluster and be proxied to the desired service on the managed cluster (can use a go client library or via http)

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• The way to use it follows the above design doc.
• cluster-proxy doesn’t support SSL server-authentication.
• cluster-proxy requires the addon users to configure the credentials of the target service in advance. (permission issue could be solved by another addon – managed-serviceaccount)

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>