To use the default setting in nf, verify that your Postgres server supports TLS 1.2 or higher versions, or set the TLS version yourself. This mirrors the setting ssl_min_protocol_version in PostgreSQL 12.x and onward.įor more information about that parameter. Constrained the valid values of this configuration option to only accept the following: tlsv1_1, tlsv1_2, tlsv1_3 or any.The default PostgreSQL SSL version has been bumped to TLS 1.2. We will stop building Alpine images and packages in Kong Gateway 3.4. These images and packages are available in 3.2 and will continue to be available in 3.3. Kong is announcing our intent to remove support for Alpine images and packages later this year.
#Alphaplugins firefor install#
To avoid this error, manually download the package from and install it.ĭeprecated Alpine Linux images and packages. The package is signed, however, it’s signed with a different (rotated) key from the metadata service, which triggers the error in yum. Due to changes in GPG keys, using yum to install this release triggers a Public key for kong-enterprise-edition-3.2.1.0. is not installed error.We plan to add the plugin back with the issues fixed in a later release. Datadog Tracing plugin: We found some late-breaking issues with the Datadog Tracing plugin and elected to remove it from the 3.2 release.The SAML plugin can now handle the field session_auth_ttl (removed since 3.2.0.0).The SAML plugin now works on read-only file systems.This file was missing in all 3.x versions of Kong Gateway prior to this release. Added the default logrotate file /etc/logrotate.d/kong-enterprise-edition.In Kong 3.2.1.0 and 3.2.1.1, alpine and ubuntu ARM64 artifacts incorrecty handled HTTP2 requests, causing the protocol to fail.Alpine deprecation reminder: Kong has announced our intent to remove support for Alpine images and packages later this year.Due to a build system issue, Kong Gateway 3.2.x packages prior to 3.2.2.1 didn’t contain the debug symbols that Dynatrace requires.
0 kommentar(er)
