-
Notifications
You must be signed in to change notification settings - Fork 18
[Feature] - service.beta.kubernetes.io/vultr-loadbalancer-timeout #285
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
Comments
@optik-aper @mondragonfx we just ran into this as well. What does it take to prioritize this issue? Thanks! |
@okdas Thanks for reaching out! I will prioritize this issue this week. |
Thank you, @mondragonfx! I also noticed that functionality is missing in vultr-cli. Will open a ticket in that repo to account for that feature. The quick solution is to update timeout via an API: curl "https://api.vultr.com/v2/load-balancers/${LB_UUID}" \
-X PATCH \
-H "Authorization: Bearer ${VULTR_API_KEY}" \
-H "Content-Type: application/json" \
--data '{
"timeout": 1800
}' Though there's no guarantee the controller won't kick it back to 600s. |
@okdas Thanks for the report I am also working on the vultr-cli as well. We are planning to cut new releases soon. |
Thanks @mondragonfx! Anything you need from us to prioritize vultr/vultr-cli#513 in the next release, just let us know! |
Uh oh!
There was an error while loading. Please reload this page.
Is your feature request related to a problem? Please describe.
I would like to ask to set up "service.beta.kubernetes.io/vultr-loadbalancer-timeout" annotation in Vultr CCM.
Describe the solution you'd like

Implementation is required for "service.beta.kubernetes.io/vultr-loadbalancer-timeout " annotation.
Describe alternatives you've considered
Setting using the attached api.
Additional context

The text was updated successfully, but these errors were encountered: