A document is needed to explain that the current support for HTTP3 is not complete.

[tao12345666333]

          @tao12345666333 Hi, according to the nginx documentation, there is no need to change OpenSSL 1.1.1 to BoringSSL:

https://nginx.org/en/docs/http/ngx_http_ssl_module.html#ssl_early_data

The directive is supported when using OpenSSL 1.1.1 or higher (1.15.4) and BoringSSL.

UPD:
I was probably not quite right, because yes, openssl supports quic, but it is incomplete support, and there are problems with some functionality(early data) and performance. But the good news is that openssl said in its roadmap that version 3.4 will have server-side support: https://www.openssl.org/roadmap.html

Also there are problems with client side: openssl/openssl#23339

Originally posted by @ipaqsa in #11172 (comment)

[k8s-ci-robot]

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[longwuyuan]

@tao12345666333 does this need to be tagged labeled as permanent-issue (visible on top of the issues list) until its behind us, sometime in the future

[tao12345666333]

/cc @ipaqsa

[tao12345666333]

@longwuyuan I don't think it's necessary at the moment because currently there are only some modifications on the NGINX side, and we haven't made any changes to the ingress-nginx controller yet.