-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot successfully register targets if VPC subnets are different from VPC CIDR block associations #3714
Comments
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:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
The text was updated successfully, but these errors were encountered: