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
Support annotations for ping services in the Helm chart #1491
Comments
Hello, nice to hear that there is a workaround for UDP, as this was the main issue left on EKS. |
Which Kubernetes version are you using? Can you please also post your Instance type?
Ideas why it still wanted to create ELB is that I used T2 instance that might not support NLB. Now I am using Kubernetes 1.15 cluster. |
There is a PR and an issue to track exact that annotation: |
Sorry, I probably shouldn't have included the NLB annotation in the udp-ping block example, since that's still blocked by #1148, which may end up being documented away, and upstream kubernetes/kubernetes#79523. Although NLB is nice-to-have, the more-important use-case for me is |
I have created initial bool version to support initial annotations here (enable/disable): |
Is your feature request related to a problem? Please describe.
Running up on AWS, we want to put an annotation on the
LoadBalancer
services to use NLB instead of ELB. This is necessary for udp (#1148) although not sufficient.This also lets us apply annotations for external-dns to get nice auto-registered DNS entries for the ping services, from the Helm config instead of later.
Describe the solution you'd like
Being able to do this in values.yaml
This should be a reasonably simple change in the Helm chart, and is pretty common in other charts. We just need to copy the blob of YAML in the annotations value into the Service.
Describe alternatives you've considered
The workaround, after installation, is to use
kubectl annotate
. Although it seems from #1148 that this won't work forservice.beta.kubernetes.io/aws-load-balancer-type
, and I haven't yet tested it withexternal-dns.alpha.kubernetes.io/hostname
Additional context
I haven't looked, but it's probably generally-useful to be able to do this for Services in a Helm chart. Allocator would definitely benefit too (also being a
LoadBalancer
by default), although I have turned that off in my deployment here.The text was updated successfully, but these errors were encountered: