Uploaded image for project: 'OpenShift Container Platform (OCP) Strategy'
  1. OpenShift Container Platform (OCP) Strategy
  2. OCPSTRAT-1738

Use internal cluster IP to connect to workload clusters

XMLWordPrintable

    • BU Product Work
    • False
    • Hide

      None

      Show
      None
    • False
    • 100% To Do, 0% In Progress, 0% Done
    • 0

      Feature goal (what are we trying to solve here?)

      Allow assisted to use internal cluster service/ip to verify or connect to workload cluster(s) in addition to the current pathway with verifying clusters via their external api address.

      Use-case is specific to hosted clusters where the workload cluster lives on the management cluster and can thereby be reached by the internal cluster ip rather than the external api address.

      DoD (Definition of Done)

      Please describe what conditions must be met in order to mark this feature as "done".

      Does it need documentation support? Yes

      If the answer is "yes", please make sure to check the corresponding option.

      Feature origin (who asked for this feature?)

      • A Customer asked for it

        • Name of the customer(s)
        • How many customers asked for it? 1 so far
        • Can we have a follow-up meeting with the customer(s)?

       

      • A solution architect asked for it

        • Name of the solution architect and contact details
        • How many solution architects asked for it?
        • Can we have a follow-up meeting with the solution architect(s)?

      Reasoning (why it’s important?)

      • If a customer using hosted control planes deploys many clusters and also uses a proxy, with our current design, they'd need to add all the dns/ips of these workload clusters to the hub's no proxy.
      • How does this feature help the product?
        • Streamlines the user experience by preventing users from having to specify their workload clusters in the no proxy configuration in advance 

      Competitor analysis reference

      • Do our competitors have this feature?
        • No idea. Need to check

      Feature usage (do we have numbers/data?)

      • Related data - the feature doesn’t exist but we have info about the usage of associated features that can help us
        • Please list all related data usage information

      Feature availability (why should/shouldn't it live inside the UI/API?)

      • Please describe the reasoning behind why it should/shouldn't live inside the UI/API
      • If it's for a specific customer we should consider using AMS
      • Does this feature exist in the UI of other installers?

      Slack threads:

      Discussion https://redhat-internal.slack.com/archives/C058TF9K37Z/p1728672610248429

      Original customer issue https://redhat-external.slack.com/archives/C01C8502FMM/p1728524011411899?thread_ts=1727471754.721429&cid=C01C8502FMM

       

            cchun@redhat.com Crystal Chun
            azaalouk Adel Zaalouk
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: