Open nullren opened 1 month ago
i've started a pr to draft out some ideas here but to also on my end to unblock my work.
one thing i'm ensure of is the "source of truth" for what the problem is, it seems there are a few things going on here:
register-targets
api actually look to just the subnets for discovery?describe-vpcs
subnets and the subnets i can see from describe-subnets
something that should be reconciled via something like sharing subnets between accounts?AvailabilityZone=all
for these? is there a reason we should not always set it?
Describe the bug the controller cannot register targets in targetgroupbinding with aws api error
this is because the registerPodEndpoints function is looking up cidr blocks associated to the vpc and not the actual subnets which is what the aws api compares.
Steps to reproduce
create vpc and associate more cidr blocks than subnets
then add a few subnets to the vpc
try to manually add a target to the target group
Expected outcome this is fixed when adding
AvailabilityZone=all
to the request and what should happen in the initial checkEnvironment
Additional Context: