community icon indicating copy to clipboard operation
community copied to clipboard

Reconcile the ACK Controllers after a CARM configmap update

Open swapnachagam opened this issue 1 year ago • 1 comments

Is your feature request related to a problem? We need to do more than 200 updates for CARM configmap as we will be onboarding more AWS accounts and our kubernetes cluster will be creating resources in multiple areas. So after the CARM configmap, instead of us manually trigger the reconcilation everytime, it would be good if ACK Controllers can do that.

Describe the solution you'd like We need ack-controllers to have a second watch for the CARM configmap updates and reconcile itself in a low priority queue? We are using many ACK controllers and also lot of AWS accounts(~200) which have to be onboarded into CARM configmap which will be done gradually. So instead of us manually doing in pre-prod and production region, we would like if controller can take care of that

Describe alternatives you've considered For now, alternative we have considered is to manually trigger the reconcilation or to restart the controllers. We are going with option for 1 project but we multiple projects using this ACK Controllers and we would like a common solution instead of us remembering to manually trigger the reconcilation

Mentioning the issue where i have discussed about this feature https://github.com/aws-controllers-k8s/community/issues/2088

swapnachagam avatar Sep 11 '24 08:09 swapnachagam

agree, faced the same issue.

gecube avatar Sep 11 '24 10:09 gecube

Issues go stale after 180d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 60d 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

ack-bot avatar Mar 10 '25 19:03 ack-bot

/remove-lifecycle stale

gecube avatar Mar 10 '25 20:03 gecube

Issues go stale after 180d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 60d 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

ack-bot avatar Sep 06 '25 21:09 ack-bot

/remove-lifecycle stale

gecube avatar Sep 06 '25 21:09 gecube