Kong 2.1.0-beta.1 released!

Hello everyone,

We recently released Kong 2.1.0-beta.1 . This is the first pre-release for the 2.1.0 series. The beta release signifies from here until 2.1.0 final we will be in feature freeze.

For folks interested in trying the beta release take note that the donwload locations were kept separated from the final release locations.

You can download packages or use the unofficial kong/kong docker repository there will be an official beta docker image in the usual location shortly

:spiral_notepad: More detail and PR links are available at the 2.1.0 Changelog .

Happy Konging!

1 Like

Oh man this is a big one for us. If I am reading this correctly in design Kong has decided to make the default behavior favorable to most users naturally(but against what NGINX with one upstream block would do by default which is only pool by IP:PORT) to ensure upstream TLS routing so that SNI/Domain for the proxy Service resource for routing is respected for connection pools, so even if sharing the same destination IPs with upstreams we will have separate connections due to their differing SNI/Domains which becomes really important on the initial handshake to ensure in scenarios like a private cloud with a single ingress IP that traffic gets routed to the correct final destinations, (which we addressed in the past with custom NGINX C code drop ins our-self Tibo had us test and try in a much earlier POC):

#upstream_keepalive_pool_size = 60  # Sets the default size of the upstream
                                    # keepalive connection pools.
                                    # Upstream keepalive connection pools
                                    # are segmented by the `dst ip/dst
                                    # port/SNI` attributes of a connection.
                                    # A value of `0` will disable upstream
                                    # keepalive connections by default, forcing
                                    # each upstream request to open a new
                                    # connection.

Really glad this made it into the flagship version to meet what I would think is a pretty common upstream pattern. Always made me nervous patching in C files manually myself :laughing: .

@jeremyjpj0916 Yes, you read that correctly :slight_smile:

1 Like

© 2019 Kong Inc.    Terms  •  Privacy  •  FAQ