-
Epic
-
Resolution: Done
-
Major
-
None
-
Single Node Console
-
False
-
False
-
Done
-
OCPPLAN-5819 - Single Node OpenShift - "Production Edge" - 4.8 - dev-preview
-
0% To Do, 0% In Progress, 100% Done
-
Undefined
-
Telco 5G RAN
Epic Goal
- Support running console in single-node OpenShift configurations for production use in edge computing use cases.
- Support disabling the console entirely in some of these configurations to reduce overhead in constrained environments.
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
- As a user, I want to deploy a fully supported instance of OpenShift on a single node.
Acceptance Criteria
- CI - MUST be running successfully with tests automated
- Release Technical Enablement - Provide necessary release enablement details and documents.
- console can be deployed with a single replica
Dependencies (internal and external)
Previous Work (Optional):
- https://github.com/openshift/enhancements/pull/504
- https://github.com/openshift/enhancements/pull/560
Open questions::
- Should the console configuration API have a separate option for this setting, or should it use the API created from
CORS-1589?
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>