Epic Goal

• Provide an API for operators to recognize the high-availability mode that should be used in a cluster.

Why is this important?

• As we create single-node deployments of OpenShift, some operators need to know whether to configure their operand in high-availability mode or to allow less fault-tolerant operation.

Scenarios

1. In the single-node production configuration, operators like the cluster-etcd-operator, cluster-authentication-operator, and cluster-ingress-operator need to configure their operands differently.

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. https://github.com/openshift/enhancements/pull/555 
2. https://github.com/openshift/enhancements/pull/560

Open questions::

1. …

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>