-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Enable http3 support for Traefik #5184
Comments
http3 support is no longer experimental as of v18.0.0 of the chart, but it still is not enabled by default. Note that due to an issue in how helm patches the service spec, you may need to delete the traefik service before applying the following config in order to get the UDP port created correctly. If you don't it simply won't expose the udp port for http3. apiVersion: helm.cattle.io/v1
kind: HelmChartConfig
metadata:
name: traefik
namespace: kube-system
spec:
valuesContent: |-
ports:
websecure:
http3:
enabled: true
advertisedPort: 443 Once this is done, I can confirm that the resulting service supports http3, although it is still notably hard to test. Here's one way: brandond@dev01:~$ docker run --rm ymuski/curl-http3 curl --http3 -vks https://172.17.0.2/
* Trying 172.17.0.2:443...
* Connect socket 5 over QUIC to 172.17.0.2:443
* Sent QUIC client Initial, ALPN: h3-29,h3-28,h3-27
* Connected to 172.17.0.2 () port 443 (#0)
* h3 [:method: GET]
* h3 [:path: /]
* h3 [:scheme: https]
* h3 [:authority: 172.17.0.2]
* h3 [user-agent: curl/7.76.1-DEV]
* h3 [accept: */*]
* Using HTTP/3 Stream ID: 0 (easy handle 0x564db63ac020)
> GET / HTTP/3
> Host: 172.17.0.2
> user-agent: curl/7.76.1-DEV
> accept: */*
>
< HTTP/3 404
< x-content-type-options: nosniff
< content-type: text/plain; charset=utf-8
<
{ [19 bytes data]
* Connection #0 to host 172.17.0.2 left intact
404 page not found |
Validated on branch 1.25 commit e212088 Infrastructure Cloud
1 server
check the ip of the new service that is created and run the docker command
< HTTP/3 404
|
I'm simply going to add this for any weary travellers who may need it: I had to manually delete both the traefik service and deployment so that the traefik service and endpoint would properly listen on both TCP and UDP. Apparently there's an issue with the traefik helm chart where it doesn't always apply the changes to these objects. |
Is your feature request related to a problem? Please describe.
Ask for by the community in this PR: #5069
Describe the solution you'd like
https://github.com/k3s-io/k3s/pull/5069/files#diff-950b8e60144da8e48c9c65a3e25d0c4cd3264400aca9bbf94d6f30e7dc2f030cR24
Describe alternatives you've considered
Additional context
Backporting
The text was updated successfully, but these errors were encountered: