Epic Goal

Introduce a new gRPC server so that the klusterlet can connect to it, avoiding any impact on the Kubernetes API server. The next step is to enable policy to connect to it.

Here is upstream issue - https://github.com/open-cluster-management-io/ocm/issues/869
 

Why is this important?

There are security concerns that the klusterlet and other addons are connecting to the hub kube api server directly.

Scenarios

Acceptance Criteria

...

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 - Doc issue opened with a completed template. Separate doc issue
  opened for any deprecation, removal, or any current known
  issue/troubleshooting removal from the doc, if applicable.