Our great sponsors
-
It's worse than that. It seems to be a Kubernetes defect around merge keys; using the port number and not the protocol + port number. https://github.com/kubernetes/kubernetes/issues/39188 But it is possible to create Kubernetes services that work correctly serving UDP and TCP on the same port; look at any old kube-dns/coredns service, for example. Indeed, I can easily create such a service for my HTTP proxy (sending TCP 443, TCP 80, and UDP 443 to my L7 proxy), but the cloud provider's software explicitly rejects it because it can't possibly work. (Meanwhile, going into their UI and modifying their object behind the k8s reconciler's back works fine, but not well enough that I trust it to announce HTTP/3 support.) I think they got spooked by a bug, but didn't realize it's a corner case and not something that happens 100% of the time. I hope it will be fixed, because I'm pretty sure they added UDP support to load balancers specifically for HTTP/3.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.