Uploaded image for project: 'On Prem Networking'
  1. On Prem Networking
  2. OPNET-133

Remote worker nodes on AI, ZTP and IPI-provisioned clusters

    XMLWordPrintable

Details

    • Remote worker nodes on AI, ZTP and IPI-provisioned clusters
    • True
    • Show
      https://issues.redhat.com/browse/OCPBUGS-7920
    • False
    • OCPSTRAT-264Compute and control plane nodes on separate subnets for on-prem IPI [ Phase 1]
    • Green
    • To Do
    • OCPSTRAT-264 - Compute and control plane nodes on separate subnets for on-prem IPI [ Phase 1]
    • Impediment
    • 100
    • 100% 100%

    Description

      Epic Goal

      As an OpenShift installation admin I want to use the Assisted Installer, ZTP and IPI installation workflows to deploy a cluster that has remote worker nodes in subnets different from the local subnet, while my VIPs with the built-in load balancing services (haproxy/keepalived).

      While this request is most common with OpenShift on bare metal, any platform using the ingress operator will benefit from this enhancement.

      Customers using platform none run external load balancers and they won't need this, this is specific for platforms deployed via AI, ZTP and IPI.

      Why is this important?

      Customers and partners want to install remote worker nodes on day1. Due to the built-in network services we provide with Assisted Installer, ZTP and IPI that manage the VIP for ingress, we need to ensure that they remain in the local subnet where the VIPs are configured.

      Previous Work

      The bare metal IPI tam added a workflow that allows to place the VIPs in the masters. While this isn't an ideal solution, this is the only option documented:

      Configuring network components to run on the control plane

      Done Checklist

      • CI - CI is running, tests are automated and merged.
      • Release Enablement <link to Feature Enablement Presentation>
      • DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
      • DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
      • DEV - Downstream build attached to advisory: <link to errata>
      • QE - Test plans in Polarion: <link or reference to Polarion>
      • QE - Automated tests merged: <link or reference to automated tests>
      • DOC - Downstream documentation merged: <link to meaningful PR>

      Attachments

        Activity

          People

            itsoiref@redhat.com Igal Tsoiref
            racedoro@redhat.com Ramon Acedo
            Dmitry Dmitriev Dmitry Dmitriev
            Shubha Narayanan Shubha Narayanan
            Votes:
            0 Vote for this issue
            Watchers:
            23 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: