Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

kubernetes.io/cluster/<cluster-name>:shared tag on unmanaged subnets won't be removed on cluster deletion #4133

Closed
wyike opened this issue Mar 8, 2023 · 3 comments
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. triage/duplicate Indicates an issue is a duplicate of other open issue.

Comments

@wyike
Copy link
Contributor

wyike commented Mar 8, 2023

/kind bug

What steps did you take and what happened:
[A clear and concise description of what the bug is.]

In BYOI https://github.com/kubernetes-sigs/cluster-api-provider-aws/blob/main/docs/book/src/topics/bring-your-own-aws-infrastructure.md case, when deleting subnets https://github.com/kubernetes-sigs/cluster-api-provider-aws/blob/main/pkg/cloud/services/network/subnets.go#L278 in ReconcileDelete cluster, it just skips the unmanaged subnets and won't remove the tags (https://github.com/kubernetes-sigs/cluster-api-provider-aws/blob/main/pkg/cloud/services/network/subnets.go#L506 kubernetes.io/cluster/<cluster-name>:shared) added for this cluster on the unmanaged subnets.

When customer have many clusters created and deleted, the tags are staled on those unmanaged subnets. Even worse, as more and more clusters create and delete, customers will hit tag limitation for these subnets in their environment. They cannot create new clusters with these unmanaged subnets and have to remove these tags manually to workaround.

What did you expect to happen:

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

  • Cluster-api-provider-aws version:
  • Kubernetes version: (use kubectl version):
  • OS (e.g. from /etc/os-release):
@k8s-ci-robot k8s-ci-robot added kind/bug Categorizes issue or PR as related to a bug. needs-priority labels Mar 8, 2023
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If CAPA/CAPI contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Mar 8, 2023
@wyike
Copy link
Contributor Author

wyike commented Mar 8, 2023

/assign

@Ankitasw
Copy link
Member

Ankitasw commented Mar 8, 2023

I have an ongoing PR for this opened. This is duplicate of #3948 and its sub-issues

@Ankitasw Ankitasw closed this as completed Mar 8, 2023
@Ankitasw Ankitasw added the triage/duplicate Indicates an issue is a duplicate of other open issue. label Mar 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. triage/duplicate Indicates an issue is a duplicate of other open issue.
Projects
None yet
Development

No branches or pull requests

3 participants