udp loadbalancer failing to create about digitalocean-cloud-controller-manager HOT 8 CLOSED

Hey @JamesBrandExpand 👋

your account also needs to be flipped on for UDP usage, which is something that our support team can do. However, that should not produce the error message you've quoted, so I'm a bit perplexed here.

Would you mind filing a support ticket please so that we can take a closer look?

from digitalocean-cloud-controller-manager.

Can do, and I will link back to this ticket in the support request. I should have mention in the original that I was advised by another team member that we dead reach out to DO and did have UDP enabled for us. I do not know the full context of the email so I may be missing information. I'm assuming that it is configured account wide and not on a per loadbalancer instance. Either way I will follow up with a support ticket for this, linking this issue.

from digitalocean-cloud-controller-manager.

Hello "another team member" here. To clarify, we did have UDP enabled for all LBs on our account last night. I can in fact see the UDP option un the DO user interface under forwarding rules. I would also note that this error was present both before and after UDP was enabled as well as before and after upgrading the cluster to 1.21.11-do.1.

from digitalocean-cloud-controller-manager.

Thanks for the extra context @kyleishie. I think the error should only show up on cluster versions older than 1.21.11-do.1 where UDP is not enabled in the cluster's backend (meaning you shouldn't see it).

We'll need to take a closer look at your cluster to see what's off. We can do so once you have submitted a support ticket. (Feel free to reference this discussion and drop my name as well for quicker correlation on our end.)

from digitalocean-cloud-controller-manager.

@timoreimann We just got a message back from DO support saying that we do NOT need to seth the protocol annotation at all and that setting a UDP port on the service is enough, per this example. We still need to set health check annotations of course. We have not tested this yet but will report back as soon as we do.

from digitalocean-cloud-controller-manager.

Oh yeah of course, support is right: for some reason my brain failed to recognize that this is about an unknown annotation, not about an unknown Service configuration field.

Thanks for the update. Looking forward to hearing if it works for you, feel free to close the ticket if it does.

from digitalocean-cloud-controller-manager.

Simply adding the port entry into our existing LoadBalancer service added the corresponding forwarding rule to the DO load balancer. I will note that this worked better than expected as we are able to use both protocols via a single LB so long as it is through different ports.

@timoreimann thanks for your help :)

from digitalocean-cloud-controller-manager.

Glad it works for you now.

from digitalocean-cloud-controller-manager.