Michael Tewoldemedhin
Michael Tewoldemedhin
> we are using gitops and rancher fleet to achive desire state. so can't use adopted resource as it required manual interventions. Hi @tomitesh, would the adoption by annotation feature...
@omri-shilton @listellm is this issue resolved for you?
All resources supported https://aws-controllers-k8s.github.io/community/reference/elbv2/v1alpha1/listener/ /close
Hi @Juricakov Of course! The changes should be part of the next release :)
Hello @Juricakov We just released a fix addressing your issue in all controllers! The IAM fix should be in [v1.3.21](https://github.com/aws-controllers-k8s/iam-controller/releases/tag/v1.3.21)
Thank you for the feedback @Juricakov. Seems like there was a bug during the update path of an adopt-or-create.
Seems like this is a dynamoDB issue..No need to create a new issue :)
Hello @jwilms1971 I am unable to replicate the issue you're having. Can you describe step by step what is happening? Here's what i tried: 1. apply an IAM Policy with...
Progress: - [ ] AccessPolicy - [x] Collection - [ ] LifecyclePolicy - [ ] SecurityConfig - [x] [SecurityPolicy](https://github.com/aws-controllers-k8s/opensearchserverless-controller/releases/tag/v0.1.0) - [ ] VpcEndpoint
Hello @michalschott @mqhenning Is this do you still have this issue? We also have a new way of adopting resources if you'd like to try that one https://aws-controllers-k8s.github.io/community/docs/user-docs/features/#resourceadoption