Skip to content
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

Ingress certificate matching does not support HTTP3 #24

Closed
drawing opened this issue Jul 24, 2023 · 1 comment · Fixed by #29
Closed

Ingress certificate matching does not support HTTP3 #24

drawing opened this issue Jul 24, 2023 · 1 comment · Fixed by #29
Assignees
Milestone

Comments

@drawing
Copy link
Collaborator

drawing commented Jul 24, 2023

Environment

Images: tengine-ingress-registry.cn-hangzhou.cr.aliyuncs.com/tengine/tengine-ingress:1.0.0

How to reproduce

Add secret for domain:

kubectl create secret tls https-server-1 --key certs/server_1_no.key --cert certs/server_1.crt

Add Ingress Config:

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: minimal-ingress
  annotations:
    nginx.ingress.kubernetes.io/ssl-redirect: "false"
spec:
  rules:
  - host: echo.test.com
    http:
      paths:
      - path: /
        pathType: Prefix
        backend:
          service:
            name: echo-service
            port:
              number: 80
  tls:
  - hosts:
    - echo.test-taobao.com
    secretName: https-server-1

A certificate is configured for domain name echo.test.com, But only http2 protocol can be matched normally, and http3 protocol certificate cannot be used.

@lianglli lianglli self-assigned this Jul 25, 2023
@lianglli lianglli added this to the 1.0.1 milestone Jul 25, 2023
@lianglli lianglli closed this as completed Aug 1, 2023
@lianglli
Copy link
Member

lianglli commented Aug 1, 2023

#29

HTTP/3: upgrade tengine 3.0.0-1 for dynamically reconfigure certificates and keys of QUIC

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants