Uploaded image for project: 'OpenShift Container Platform (OCP) Strategy'
  1. OpenShift Container Platform (OCP) Strategy
  2. OCPSTRAT-339

[Phase 2] Add a new platform type ("external") to identify clusters with non-integrated partner components enabled


    • False
    • Hide


    • False
    • OCPSTRAT-10Install and update OpenShift on Infrastructure Providers
    • 0% To Do, 0% In Progress, 100% Done
    • 0
    • 0
    • Program Call

      OCP/Telco Definition of Done
      Epic Template descriptions and documentation.

      <--- Cut-n-Paste the entire contents of this description into your new Epic --->

      Feature Goal

      • Enable platform=external to support onboarding new partners, e.g. Oracle Cloud Infrastructure and VCSP partners.
      • Create a new platform type, working name "External", that will signify when a cluster is deployed on a partner infrastructure where core cluster components have been replaced by the partner. “External” is different from our current platform types in that it will signal that the infrastructure is specifically not “None” or any of the known providers (eg AWS, GCP, etc). This will allow infrastructure partners to clearly designate when their OpenShift deployments contain components that replace the core Red Hat components.

      This work will require updates to the core OpenShift API repository to add the new platform type, and then a distribution of this change to all components that use the platform type information. For components that partners might replace, per-component action will need to be taken, with the project team's guidance, to ensure that the component properly handles the "External" platform. These changes will look slightly different for each component.

      To integrate these changes more easily into OpenShift, it is possible to take a multi-phase approach which could be spread over a release boundary (eg phase 1 is done in 4.X, phase 2 is done in 4.X+1).

      OCPBU-5: Phase 1

      • Write platform “External” enhancement.
      • Evaluate changes to cluster capability annotations to ensure coverage for all replaceable components.
      • Meet with component teams to plan specific changes that will allow for supplement or replacement under platform "External".
      • Start implementing changes towards Phase 2.

      OCPBU-510: Phase 2

      • Update OpenShift API with new platform and ensure all components have updated dependencies.
      • Update capabilities API to include coverage for all replaceable components.
      • Ensure all Red Hat operators tolerate the "External" platform and treat it the same as "None" platform.

      OCPBU-329: Phase.Next

      • TBD

      Why is this important?

      • As partners begin to supplement OpenShift's core functionality with their own platform specific components, having a way to recognize clusters that are in this state helps Red Hat created components to know when they should expect their functionality to be replaced or supplemented. Adding a new platform type is a significant data point that will allow Red Hat components to understand the cluster configuration and make any specific adjustments to their operation while a partner's component may be performing a similar duty.
      • The new platform type also helps with support to give a clear signal that a cluster has modifications to its core components that might require additional interaction with the partner instead of Red Hat. When combined with the cluster capabilities configuration, the platform "External" can be used to positively identify when a cluster is being supplemented by a partner, and which components are being supplemented or replaced.


      1. A partner wishes to replace the Machine controller with a custom version that they have written for their infrastructure. Setting the platform to "External" and advertising the Machine API capability gives a clear signal to the Red Hat created Machine API components that they should start the infrastructure generic controllers but not start a Machine controller.
      2. A partner wishes to add their own Cloud Controller Manager (CCM) written for their infrastructure. Setting the platform to "External" and advertising the CCM capability gives a clear to the Red Hat created CCM operator that the cluster should be configured for an external CCM that will be managed outside the operator. Although the Red Hat operator will not provide this functionality, it will configure the cluster to expect a CCM.

      Acceptance Criteria

      Phase 1

      • Partners can read "External" platform enhancement and plan for their platform integrations.
      • Teams can view jira cards for component changes and capability updates and plan their work as appropriate.

      Phase 2

      • Components running in cluster can detect the “External” platform through the Infrastructure config API
      • Components running in cluster react to “External” platform as if it is “None” platform
      • Partners can disable any of the platform specific components through the capabilities API

      Phase 3

      • Components running in cluster react to the “External” platform based on their function.
        • for example, the Machine API Operator needs to run a set of controllers that are platform agnostic when running in platform “External” mode.
        • the specific component reactions are difficult to predict currently, this criteria could change based on the output of phase 1.

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      1. Identifying OpenShift Components for Install Flexibility

      Open questions::

      1. Phase 1 requires talking with several component teams, the specific action that will be needed will depend on the needs of the specific component. At the least the components need to treat platform "External" as "None", but there could be more changes depending on the component (eg Machine API Operator running non-platform specific controllers).

      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>

            julim Ju Lim
            mimccune@redhat.com Michael McCune
            Jianwei Hou Jianwei Hou
            Stephanie Stout Stephanie Stout
            Michael McCune Michael McCune
            Chris Fields Chris Fields
            0 Vote for this issue
            13 Start watching this issue