THERE ISN'T MUCH POINT TO HTTP/2 PAST THE LOAD BALANCER

Summary from the TLDR Web Dev newsletter

HTTP/2 support in Ruby HTTP servers like Puma isn't necessary because its primary benefit, multiplexing, is most impactful over the internet with high latency. Within a datacenter, the low latency between the application server and load balancer takes away the advantage of HTTP/2. Furthermore, features like server push, once a motivation for end-to-end HTTP/2, have been abandoned, so HTTP/2 is best handled at the infrastructure entry point (load balancer or reverse proxy) to avoid unnecessary complexity within the application server.