Uploaded image for project: 'OpenShift Installer'
  1. OpenShift Installer
  2. CORS-2667

Compact 3-node clusters IPI support on Nutanix

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Normal Normal
    • openshift-4.14
    • None
    • None
    • None
    • Compact 3-node clusters support on Nutanix
    • BU Product Work
    • False
    • None
    • False
    • Not Selected
    • Done
    • OCPSTRAT-556 - Compact 3-node clusters support in Nutanix
    • OCPSTRAT-556Compact 3-node clusters support in Nutanix
    • 0% To Do, 0% In Progress, 100% Done

      Goal: 

      As an administrator, I should be able to install a 3-node cluster (no workers) on the Nutanix platform via the IPI installation paths, and have a fully conformant OpenShift cluster (all features enabled).

      Problem:

      OpenShift is intended to run in a wide variety of environments. Over the years we have refined and reduced the default required footprint - first by removing the hard requirement for infrastructure nodes in 4.1, and second by preparing for 3-node clusters in 4.2 with the introduction of the masterSchedulable flag. OpenShift should continue to take steps to reduce the default footprint and incentivize improvements that allow it to work with smaller 3-node and eventually one node clusters.

      Lifecycle Information:

      • Core

      Deliverables (in scope / not in scope):

      • Allow pods to be schedulable on Master Nodes when a 3-node cluster is deployed
      • Automatically place router pods on Masters if no worker nodes are present
      • Ensure 3-node clusters work correctly in Nutanix environments
      • Support transitioning to a larger cluster and make the control plane unschedulable.
      • Add compact 3-node cluster configurations to CI test system

              yanhli@redhat.com Yanhua Li
              racedoro@redhat.com Ramon Acedo
              Shang Gao Shang Gao
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: