Epic Goal

Support the ability for a proxy connection between the global hub and managed hub cluster

Why is this important?

• Customers have scenarios where firewalls may be in place between where the global hub is located and where the managed hub is located.
• Global hub's networking model leverages an mTLS connection from the managed hub cluster to the global hub api server.  
• Global hub agent needs to access the Kafka route which is located in the global hub for any chance.

Scenarios

• Support Use Case 1 and Use Case 2:
  • Need know the network topology for global hub cluster and managed hub cluster from the customer.
    **

Acceptance Criteria

• Leverages the global proxy setting when present on the ManagedCluster
• Can be overridden.

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>