-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.18.0
-
Important
-
Yes
-
Rejected
-
False
-
Description of problem:
Destroying a private cluster doesn't delete the forwarding-rule/backend-service/health-check/firewall-rules created by ingress operator.
Version-Release number of selected component (if applicable):
4.18.0-0.nightly-multi-2024-10-23-202329
How reproducible:
Always
Steps to Reproduce:
1. pre-create vpc network/subnets/router and a bastion host 2. "create install-config", and then insert the network settings under platform.gcp, along with "publish: Internal" (see [1]) 3. "create cluster" (use the above bastion host as http proxy) 4. "destroy cluster" (see [2])
Actual results:
Although "destroy cluster" completes successfully, the forwarding-rule/backend-service/health-check/firewall-rules created by ingress operator are not deleted (see [3]), which leads to deleting the vpc network/subnets failure.
Expected results:
The forwarding-rule/backend-service/health-check/firewall-rules created by ingress operator should also be deleted during "destroy cluster".
Additional info:
FYI one history bug https://issues.redhat.com/browse/OCPBUGS-37683