Uploaded image for project: 'OpenShift Specialist Platform Team'
  1. OpenShift Specialist Platform Team
  2. SPLAT-827

[Technology Preview] Support static IP assignments with vSphere IPI

Details

    • Epic
    • Resolution: Done
    • Major
    • openshift-4.14
    • None
    • Support static IP assignments with vSphere IPI
    • False
    • None
    • False
    • Not Selected
    • To Do
    • OCPSTRAT-130 - [Technology Preview] Support static IP assignments with vSphere IPI
    • OCPSTRAT-130[Technology Preview] Support static IP assignments with vSphere IPI
    • 100
    • 100% 100%

    Description

      Epic Goal

      As an OpenShift on vSphere administrator, I want to specify static IP assignments to my VMs.

      As an OpenShift on vSphere administrator, I want to completely avoid using a DHCP server for the VMs of my OpenShift cluster.

      Why is this important?

      Customers want the convenience of IPI deployments for vSphere without having to use DHCP. As in bare metal, where METAL-1 added this capability, some of the reasons are the security implications of DHCP (customers report that for example depending on configuration they allow any device to get in the network). At the same time IPI deployments only require to our OpenShift installation software, while with UPI they would need automation software that in secure environments they would have to certify along with OpenShift.

      Acceptance Criteria

      • I can specify static IPs for node VMs at install time with IPI

      Previous Work

      Bare metal related work:

      CoreOS Afterburn:

      https://github.com/coreos/afterburn/blob/main/src/providers/vmware/amd64.rs#L28

      https://github.com/openshift/installer/blob/master/upi/vsphere/vm/main.tf#L34

      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

            rhn-support-rvanderp Richard Vanderpool
            rhn-support-rvanderp Richard Vanderpool
            Shang Gao Shang Gao
            Votes:
            5 Vote for this issue
            Watchers:
            9 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: