kubernetes-sigs/cluster-api-provider-aws

Allow `shared` tag value for AWS resource import

kahirokunn opened this issue · 3 comments

kahirokunn commented

Describe the solution you'd like
Currently, the implementation only supports the owned tag value for AWS resource imports. I would like to request that the shared tag value also be supported. This enhancement is important because creating resources with the owned tag leads to potential risks when the Cluster is deleted, as it attempts to delete the network associated with it. There is a risk that other services, such as Load Balancers or other deployments, could be relying on that network, leading to unintended disruptions.

Anything else you would like to add:
Allowing the shared tag value will provide greater flexibility and safety in managing AWS resources within shared environments. This change will help avoid accidental deletions of critical network infrastructure that might be shared across multiple services or applications.

Environment:

  • Cluster-api-provider-aws version: v2.5.0
  • Kubernetes version: (use kubectl version): v1.30.1
  • OS (e.g. from /etc/os-release): M1 MacOS
k8s-ci-robot commented

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-sigs/prow repository.

k8s-triage-robot commented

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

kahirokunn commented

/remove-lifecycle stale