Open aayushrangwala opened 1 year ago
/assign @aayushrangwala
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/reopen
/remove-lifecycle rotten
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
/reopen
@cprivitere: Reopened this issue.
/triage accepted
/remove-lifecycle rotten
What steps did you take and what happened:
The clusters created using Cluster API provider packet and Cloud Provider Equinix Metal assigns an public Elastic IP to the devices. It does not get cleaned up even after all the resources are deleted.
Deletion of the cluster is done using
kubectl delete cluster -A
and the cluster also got deleted from k8s and equinix consoleWhat did you expect to happen: All the resources created by CPEM and CAPI provider should be cleaned up. If there are any errors, it should display warnings for the remaining resources for which the cleanup has to be manual from console
Environment:
kubectl version
): v1.27/etc/os-release
): MacOS