-
Feature
-
Resolution: Unresolved
-
Major
-
None
-
None
-
BU Product Work
-
False
-
-
False
-
50% To Do, 50% In Progress, 0% Done
-
7
-
0
Feature Overview (aka. Goal Summary)
Have Hosted Cluster's cloud resource cleanup be directly managed by HyperShift instead of delegating to the operators that run in the Hosted Control Plane so that we can achieve better SLO performance and more control over what fails to delete.
Goals (aka. expected user outcomes)
- Quicker cloud resource deletion
- Information about resources that can't be deleted
Requirements (aka. Acceptance Criteria):
- Keep with cloud resource deletion SLO
- Metrics agreed with SRE on resources that can't be deleted
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 | both |
| Classic (standalone cluster) | no |
| Hosted control planes | yes |
| Multi node, Compact (three node), or Single node (SNO), or all | All supported Hosted Control Planes topologies and configurations |
| Connected / Restricted Network | All supported Hosted Control Planes topologies and configurations |
| Architectures, e.g. x86_x64, ARM (aarch64), IBM Power (ppc64le), and IBM Z (s390x) | All supported Hosted Control Planes topologies and configurations |
| Operator compatibility | N/A |
| Backport needed (list applicable versions) | No |
| UI need (e.g. OpenShift Console, dynamic plugin, OCM) | Maybe the failure to delete resources could be shown in the console. |
| Other (please specify) |
Use Cases (Optional):
- Hosted Cluster is successfully deleted within SLO time
- Hosted Cluster fails to have some resources deleted (typically due to permissions changes) and emits metrics to make it observable.
Out of Scope
Background
The OpenShift installer and Hive manage it this way
Customer Considerations
We need to come up with the right level of granularity for the emitted metrics and the right UX to show it
Documentation Considerations
The metrics and the UX need to be documented. An SOP for tracking failures should be written.
Interoperability Considerations
ROSA/HCP and ARO/HCP
