Multiple adopted resources can create duplicate resources
Describe the bug
Two uniquely named AdoptedResource types referencing the same nameOrID or ARN can independently create two new K8s ACK resources that reference the same AWS resource. This could result in multiple ACK resources fighting over source-of-truth if either of them changes the specification.
Steps to reproduce
- Adopt an S3 bucket with one
AdoptedResource - Adopt the same S3 bucket with another
AdoptedResourceof a different name - Check to see that both buckets appear to be managed by ACK
Expected outcome Some sort of warning should be placed on the second adopted resource that clearly states the target AWS resource is already being managed. The second adopted resource should not create any additional resources.
Environment
- Kubernetes version
- Using EKS (yes/no), if so version?
- AWS service targeted (S3, RDS, etc.)
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/aws-controllers-k8s/community.
/lifecycle stale
/remove-lifecycle stale
/lifecycle frozen
can someone pick this up and verify if we see the same issue via adoption through annotations?
I'm unsure of a gitops use case with same resource being adopted twice.. @michaelhtm you think we'd need to look into this adoption by annotation? is this something we should be concerned about?
cc @knottnt @a-hilaly
We haven't seen any customer created issues for this. If we do, it would still be relevant for adoption by annotation as well
I see we can close this then. /close
@rushmash91: Closing this issue.
In response to this:
I see we can close this then. /close
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.