Uploaded image for project: 'OpenShift Top Level Product Strategy'
  1. OpenShift Top Level Product Strategy
  2. OCPPLAN-9446

Ensure openshift-dns-operator is running on hosted control planes

    XMLWordPrintable

Details

    • Epic
    • Resolution: Duplicate
    • Blocker
    • None
    • None
    • None
    • Ensure openshift-dns-operator is running on hosted control planes
    • False
    • None
    • False
    • Not Selected
    • ?
    • No
    • ?
    • To Do
    • OCPSTRAT-103 - Ensuring the Control Plane is Fully Decoupled for Hosted Control Planes
    • ?
    • OCPSTRAT-103Ensuring the Control Plane is Fully Decoupled for Hosted Control Planes
    • ?
    • 100
    • 100% 100%
    • Approved

    Description

      Overview 

      Customers do not pay Red Hat more to run HyperShift control planes and supporting infrastructure than Standalone control planes and supporting infrastructure.

      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.

      DoD 

      • openshift-dns-operator controller is running on the CP. 
      • A CI hypershift presubmit runs on the operator repo.

      More information here: https://docs.google.com/document/d/1sXCaRt3PE0iFmq7ei0Yb1svqzY9bygR5IprjgioRkjc/edit 

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              azaalouk Adel Zaalouk
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: