Epic Goal

• Support deploying single-node OpenShift configurations for production use in edge computing use cases.

Why is this important?

• Some bare metal edge customers, especially in the telco market, want to use kubernetes at physically remote sites with minimal hardware.

Scenarios

1. As a deployer, I can use the installer to configure a single-node OpenShift cluster.
2. As an operator author, I can use an API within the cluster to detect the single-node configuration and adjust my operand accordingly.

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/565
2. https://github.com/openshift/enhancements/pull/560
3. OCP Single Node Production Edge Profile

Open questions::

1. What should the input for specifying a single-node cluster look like?
2. What should the API for discovering that a cluster is single-node look like?

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>