-
Story
-
Resolution: Done
-
Blocker
-
None
-
None
-
None
-
False
-
None
-
False
-
Hypershift Sprint 15, Hypershift Sprint 16
-
0
-
0
-
0
Currently, any cloud resources like load balancers and volumes that are created by a controller running against the hostedcluster KAS will be left behind when deleting a hostedcluster. We should make their cleanup part of hostedcluster deletion:
AC:
- Hostedcluster deletion triggers cleanup of all LBs created for it
- Hostedcluster deletion triggers cleanup of all PVs created for it
- Hostedcluster deletion triggers the cleanup of the registry bucket
- Any other cloud resources created by controller running against the hosted cluster KAS get cleaned up
- relates to
-
HOSTEDCP-656 Hosted cluster deletion does not clean up elb security group
- Closed
-
OCPSTRAT-591 HyperShift Core Component Readiness for GA - Part I
- Closed
- links to