Uploaded image for project: 'OpenShift Edge Enablement'
  1. OpenShift Edge Enablement
  2. OCPEDGE-1191

Support 2+1 with Local Arbiter Node Configuration for Control Plane Topology

XMLWordPrintable

    • Support 2+1 with Local Arbiter Node Configuration for Control Plane Topology
    • Product / Portfolio Work
    • OCPSTRAT-1500Two Node OpenShift with Arbiter (TNA) - Tech Preview
    • 0% To Do, 0% In Progress, 100% Done
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • XL
    • 78

      Goal:

      When we say co-located we mean a typical install with either 3 machines next to each other, or 3 machines in a datacenter such as AWS instances in the same VPC.

      As an administrator I would like to be able to install OpenShift on 2 nodes that follow the recommendation for OCP node size, and 1 smaller less powerful for only critical systems to facilitate HA.

      Non-Goal:

      We will not currently support remote and or VM locations for the single less powerful node.

      *Key results: *

      At minimum we would like to be in Tech Preview for a 2+1 installation of OCP for this release.

      Acceptance criteria:

      • Installing the cluster with 2 regular nodes and 1 less powerful node
      • Only critical workloads should run on smaller node but
      • Cluster can be upgraded to regular 3 node cluster and full OCP cluster
      • CI lane to validate installation is functioning

      Open Questions:

      Having a single less powerful node that will contain a full ETCD member might require extra attention from the ETCD team to help determine proper tuning, ETCD performance might suffer if that single member struggles.

              ehila@redhat.com Egli Hila
              ehila@redhat.com Egli Hila
              None
              Geri Peterson Geri Peterson
              Neil Hamza Neil Hamza
              Srikanth R Srikanth R
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: