Installing OCS/ODF in a Private OpenShift cluster creates Public IPs

Solution Verified - Updated -

Environment

  • Red Hat OpenShift Container Storage (RHOCS)
    • 4
  • Red Hat OpenShift Data Foundation (RHODF)
    • 4
  • Red Hat OpenShift Container Platform (RHOCP)
    • 4
  • Azure Red Hat OpenShift (ARO)
    • 4
  • OpenShift Managed (Azure)
    • 4

Issue

  • Installing MCG (NooBaa) in a Private OCP creates public facings ELBs that make the Private cluster Public.
  • Public IPs have been created for Private ARO Cluster after installing OCS/ODF.

Resolution

This behavior was fixed in ODF 4.10 by BZ 1954708 in errata RHSA-2022:1372.

The flag disable-load-balancer was added to NooBaa in ODF 4.10 as shown in the release notes.

An internal RFE (RHSTOR-3345) was created to allow to use the flag during ODF installation.

Root Cause

Starting with ODF 4.10, a new flag was added (disable-load-balancer) that replaces the type of service from LoadBalancer to ClusterIP. This flag allows to disable the NooBaa service EXTERNAL-IP.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments