-
Notifications
You must be signed in to change notification settings - Fork 39.8k
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
Respect Allocation IDs #69263
Respect Allocation IDs #69263
Conversation
/assign @justinsb |
@brooksgarrett Thanks for your first contribution to Kubernetes! 🎉 /ok-to-test This change it looks like a release note? |
I'm AFK today but will document it tomorrow. |
Have we tested this? Or already covered somewhere? |
I'm currently rolling it into our soak environment today. It was approved for test over the weekend so I'm just now able to get the binaries rolled out. I tested it in local go harnesses before implementing but as seen with the quoted variable issue I may have bugs. I'll comment here with clear results of testing by tomorrow or Wednesday (3 Oct). |
Tested this on a kops deployed cluster on AWS. Cluster spans over 3 AZs. Created a service with 3 EIP allocations. NLB was created correctly and EIPs are correctly associated with the ENIs. |
Is anything else needed for this PR? |
1 similar comment
Is anything else needed for this PR? |
Pinging assignee @justinsb for an update. Our company would desperately like this in. |
/assign @M00nF1sh |
I'll take a look later today. |
Thank you |
Rebased |
Hi @justinsb, Hi @chrislovecnm When you will have time, please can you review the pull request that it's described below? Thank you. |
response = append(response, &elbv2.SubnetMapping{SubnetId: aws.String(id)}) | ||
for index, id := range subnetIDs { | ||
sm := &elbv2.SubnetMapping{SubnetId: aws.String(id)} | ||
if len(allocationIDs) > 0 { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
len(allocationIDs)>index+1
might be better to understand.
But keep it as it is good enough too(relying on the fact allocationIDs will be either 0 or equal to length of subnetIDs at caller-side).
/lgtm |
Hi team, What will be the next step for this pull request? Thank you |
/assign @micahhausler |
/approve |
@brooksgarrett commit messages that at-mention people are no longer permitted for merge in Kubernetes. Would you please either fix the commit message mentioning @gyuho or squash all of these commits into one and update this PR. I'll re-lgtm and approve after that push. Thanks! |
Hi @brooksgarrett, |
bd2f767
to
7767535
Compare
@mcrute Squashed all commits down per request. |
Thanks! /lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: brooksgarrett, mcrute The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Thank you so much @brooksgarrett 🥇 |
How to get Allocation IDs? |
What this PR does / why we need it:
AWS NLB supports the use of static IP addresses (EIP) with Network Load Balancers. This PR supports a new annotation on services
service.beta.kubernetes.io/aws-load-balancer-eip-allocations
which is a comma separated list of AWS Allocation IDs. The number of Allocation IDs must match the number of subnets used for the load balancer./kind feature
/sig aws
Fixes #63959
Special notes for your reviewer:
None
Release note: