-
Epic
-
Resolution: Unresolved
-
Major
-
None
-
None
-
IBM Cloud Service endpoints should be able to change day 2
-
Product / Portfolio Work
-
-
100% To Do, 0% In Progress, 0% Done
-
False
-
-
False
-
Not Selected
-
None
-
None
-
None
OCP/Telco Definition of Done
Epic Template descriptions and documentation.
<--- Cut-n-Paste the entire contents of this description into your new Epic --->
Epic Goal
- The Infrastructure object contains information in the status to be able to configure service endpoint overrides, which are then consumed by operators to know where IBM APIs live, in particular, the cloud controller manager.
- We need to provide a way for these to be updated over time, by adding a spec field and then having an controller somewhere validate and copy the changes to the status.
- Consumers should remain leveraging the status.
Why is this important?
- Over time, we expect the endpoints to change within IBM, but we want to keep IBM management clusters (barges) around for a long time, beyond these endpoints updating.
Scenarios
- ...
Acceptance Criteria
- CI - MUST be running successfully with tests automated
- Release Technical Enablement - Provide necessary release enablement details and documents.
- ...
Dependencies (internal and external)
- ...
Previous Work (Optional):
- …
Open questions::
- …
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>
- links to
