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

Ensuring the Control Plane is Fully Decoupled for Hosted Control Planes

XMLWordPrintable

    • BU Product Work
    • False
    • Hide

      None

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

       

      Why?

      • Decouple control and data plane. 
        • Customers do not pay Red Hat more to run HyperShift control planes and supporting infrastructure than Standalone control planes and supporting infrastructure.
      • Improve security
        • Shift credentials out of cluster that support the operation of core platform vs workload
      • Improve cost
        • Allow a user to toggle what they don’t need.
        • Ensure a smooth path to scale to 0 workers and upgrade with 0 workers.

       

      Assumption

      • A customer will be able to associate a cluster as “Infrastructure only”
      • E.g. one option: management cluster has role=master, and role=infra nodes only, control planes are packed on role=infra nodes
      • OR the entire cluster is labeled infrastructure , and node roles are ignored.
      • Anything that runs on a master node by default in Standalone that is present in HyperShift MUST be hosted and not run on a customer worker node.

       

       

      Doc: https://docs.google.com/document/d/1sXCaRt3PE0iFmq7ei0Yb1svqzY9bygR5IprjgioRkjc/edit 

            azaalouk Adel Zaalouk
            azaalouk Adel Zaalouk
            Alberto Garcia Lamela Alberto Garcia Lamela
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: