-
Feature
-
Resolution: Unresolved
-
Major
-
None
-
None
-
BU Product Work
-
False
-
-
False
-
50% To Do, 50% In Progress, 0% Done
-
0
-
Program Call
Feature Overview (aka. Goal Summary)
(This is a user-facing capability breakout from OCPSTRAT-714)
The ability for OpenShift components to recover from expired certificates when the cluster has been shutdown or in hibernation for up to 6 months)
Goals (aka. expected user outcomes)
The observable functionality that the user now has as a result of receiving this feature. Include the anticipated primary user type/persona and which existing features, if any, will be expanded. Complete during New status.
Ability to recover self-managed OpenShift control plane from expired certificate resulting from a cluster shutdown or hibernation for 3 to 6 months.
This feature can be broken into two phases:
- Phase 1: shutdown or hibernation for up to 90 days
- Phase 2: shutdown or hibernation for up to 180 days
Requirements (aka. Acceptance Criteria):
A list of specific needs or objectives that a feature must deliver in order to be considered complete. Be sure to include nonfunctional requirements such as security, reliability, performance, maintainability, scalability, usability, etc. Initial completion during Refinement status.
CI-test validating self-managed OpenShift control-plane recovering automatically after cluster hibernated for up to 6 months.
Anyone reviewing this Feature needs to know which deployment configurations that the Feature will apply to (or not) once it's been completed. Describe specific needs (or indicate N/A) for each of the following deployment scenarios. For specific configurations that are out-of-scope for a given release, ensure you provide the OCPSTRAT (for the future to be supported configuration) as well.
Deployment considerations | List applicable specific needs (N/A = not applicable) |
Self-managed, managed, or both | self-managed |
Classic (standalone cluster) | yes |
Hosted control planes | N/A |
Multi node, Compact (three node), or Single node (SNO), or all | multi-node and compact clusters |
Connected / Restricted Network | both |
Architectures, e.g. x86_x64, ARM (aarch64), IBM Power (ppc64le), and IBM Z (s390x) | all |
Operator compatibility | cluster operators |
Backport needed (list applicable versions) | N/A |
UI need (e.g. OpenShift Console, dynamic plugin, OCM) | N/A |
Other (please specify) | N/A |
Use Cases (Optional):
Include use case diagrams, main success scenarios, alternative flow scenarios. Initial completion during Refinement status.
<your text here>
Questions to Answer (Optional):
Include a list of refinement / architectural questions that may need to be answered before coding can begin. Initial completion during Refinement status.
<your text here>
Out of Scope
High-level list of items that are out of scope. Initial completion during Refinement status.
<your text here>
Background
Provide any additional context is needed to frame the feature. Initial completion during Refinement status.
<your text here>
Customer Considerations
Provide any additional customer-specific considerations that must be made when designing and delivering the Feature. Initial completion during Refinement status.
<your text here>
Documentation Considerations
Provide information that needs to be considered and planned so that documentation will meet customer needs. If the feature extends existing functionality, provide a link to its current documentation. Initial completion during Refinement status.
<your text here>
Interoperability Considerations
Which other projects, including ROSA/OSD/ARO, and versions in our portfolio does this feature impact? What interoperability test scenarios should be factored by the layered products? Initial completion during Refinement status.
<your text here>
- blocks
-
OCPSTRAT-1483 Capability to trigger full shutdown of an OpenShift cluster
- New
-
OCPSTRAT-714 Provide Detailed Administrative Control of all OCP Certs and Keys
- In Progress
- depends on
-
API-1800 Migrate secrets of "SecretTypeTLS" type
- Closed
- is depended on by
-
OCPSTRAT-1403 Automated control-plane recovery from invalidated certificates (node identity)
- New
-
OCPSTRAT-539 Enhance recovery procedure for full control plane failure
- In Progress
- is incorporated by
-
API-1689 Create TLS artifacts registry
- In Progress
-
API-1800 Migrate secrets of "SecretTypeTLS" type
- Closed
- is related to
-
OCPSTRAT-1199 4 and 5-nodes control-plane architecture for bare-metal spanned clusters
- Closed
- split to
-
OCPSTRAT-1403 Automated control-plane recovery from invalidated certificates (node identity)
- New