title: How to attach multiple elastic IPs to one aws network load balancer deployed on EKS and make all those IPs available?
body: <p>I create a EKS cluster and deploy a K8S service according to the docuements on AWS, and the NLB is working, but as other questions on StackOverflow have mentioned, if the service got deleted the external IP of the NLB will change, so I want to attch some elastic IPs to the NLB. And after some google, I add these annotations on the yaml of my service</p>
  <pre><code>service.beta.kubernetes.io/aws-load-balancer-eip-allocations: eipalloc-06984171f8612ccfa,eipalloc-027c0ee7a8be0f94f
  service.beta.kubernetes.io/aws-load-balancer-subnets: subnet-0d327a9b0a60e47c2,subnet-0e19bf141f1bba31a
  service.beta.kubernetes.io/aws-load-balancer-nlb-target-type: ip
  service.beta.kubernetes.io/aws-load-balancer-scheme: internet-facing
  service.beta.kubernetes.io/aws-load-balancer-type: external
  </code></pre>
  <p>As you can see, I attached 2 EIPs and 2 subnets to the NLB, right now the problem is that only the first EIP works, I can't ping the second EIP, and if I switch the order of the 2 EIPs, then the working EIP will change to the new first one.</p>
  <p>So is this behaviour by designed? Or am I missing some annotations or some configurations on AWS?</p>
  <p>And if this is by designed, will aws auto switch to the second EIP if the first EIP is down?</p>
  <p>Also is attach EIPs to NLB a normal practice or is there any better ones?</p>
  <p>Thanks!</p>