Time for a new release candidate Kong folks!
This is the second release candidate for our next release, Kong 1.2.0rc2 !
The release brings improvements to reduce P95 latency and consolidates declarative configuration support . It also comes with newly open sourced plugins , previously only available to Enterprise customers, and a few features around usability.
Download Kong 1.2.0rc2 today — as always we are looking forward for your feedback!
All Bintray repositories have been renamed from
All Kong packages have been renamed from
For more details about the updated installation, please visit the official docs: https://konghq.com/install.
What’s New since Kong 1.2.0rc1
- Schema fields can now be marked immutable
- DAO operations can now be passed a new options
no_broadcast_crud_eventto prevent Kong firing the worker events.
- Fix to an issue introduced in
init_workerwas not being called on plugins that implemented it
request-transformer-advanced(previously only available in Enterprise) plugins were merged
- Fix to an issue where
:newwas not always called when Plugins deep-inherited from BasePlugin
db_importto upsert via deterministic v5 UUIDs
And a recap of all the new stuff in the 1.2.0 release candidate series
Asynchronous router updates: introduce a configuration properties
router_consistency, with two possible values:
eventual. If set to
eventual, whenever your Kong configuration changes, router update operations are performed out of the proxy path, asynchronously, reducing P95 latency when performing runtime Services/Routes manipulation.
Cache warmup of Kong entities at initialization. A new configuration directive
db_cache_warmup_entitieswas introduced, allowing users to specify which entities should be preloaded. Cache warmup allows for ahead of time DNS resolution for Services with a hostname. This feature reduces first requests latency, improving P99 latency.
Wildcard SNI matching: the
ssl_certificate_by_luaphase (and stream preread) is now able to match an SNI against any registered wildcard SNI.
HTTPS routes can now be matched by SNI : the
snisroute attribute can now be set for HTTPS routes and is used as a routing attribute
- New optional configuration properties for PostgreSQL concurrency control:
pg_max_concurrent_queriessets the maximum number of concurrent queries to the database;
pg_semaphore_timeoutallows you to tune the timeout for acquiring access to the database connection. The default behavior remains the same, with no concurrency limitation.
- Asynchronous router updates: introduce a configuration properties
Hash checking for declarative configuration, avoiding reloading if the configuration has not changed. The
/configendpoint now accepts a
check_hashquery argument; hash checking only happens if its value is set to
- The loading of declarative configuration is now done atomically, and with a safety check to verify that the new configuration fits in memory.
- Hash checking for declarative configuration, avoiding reloading if the configuration has not changed. The
Entity schema validation endpoints: you can use the new endpoint
/schemas/:entity_name/validateto validate an instance of any entity type in Kong without creating the entity
Memory statistics in the
/statusendpoint. The response now includes a
memoryfield, which contains
workers_lua_vms, with stats on shared dictionaries and workers Lua VM memory usage.
- Entity schema validation endpoints: you can use the new endpoint
- proxy-cache: we open sourced the HTTP proxy cache plugin, previously an Enterprise-only feature
- New data available for logging plugins: log request TLS version, cipher, and verification status.
- New function
- Inheriting from
BasePluginis now optional
- New function
Plus of course the usual amount of bugfixes and internal improvements!
You can upgrade from 0.14.1 or any release in the 1.x series (Note: upgrading from a pre-0.14 cluster is not supported). You can use a Blue/Green deployment method to update: “Blue” means your current version (for example, 0.14.1, 1.0.x or 1.1.x), “Green” means the new version 1.2.0rc2:
- Download 1.2.0rc2, and configure it to point to the same datastore as your Blue cluster (running 0.14, 1.0 or 1.1). Run
kong migrations up.
- Both Blue and Green nodes can now run simultaneously on the same datastore. Start provisioning 1.2.0rc1 nodes, but do not use their Admin API yet. Prefer making Admin API requests to your Blue cluster instead.
- Gradually divert traffic away from your Blue nodes, and into your 1.2.0rc2 cluster. Monitor your traffic to make sure everything is going smoothly.
- When your traffic is fully migrated to the Green 1.2.0rc2 cluster, decommission your Blue nodes.
- From your 1.2.0rc2 cluster, run:
kong migrations finish. From this point on, it will not be possible to start Blue nodes pointing to the same datastore anymore. Only run this command when you are confident that your migration was successful. From now on, you can safely make Admin API requests to your 1.2.0rc2 nodes.
Install 1.2.0rc2 on a fresh datastore
Since version 1.0, Kong uses a new, improved migrations framework. The following commands can be run to prepare a new 1.2 cluster from a fresh datastore:
$ kong migrations bootstrap [-c kong.conf] $ kong start [-c kong.conf]
Depeding on the community feedback, we are going to either tag and release 1.2.0 final or make a new release candidate 1.2.0rc3.
As always, consider yourself encouraged to reach out to us here or via GitHub issues if you have any questions or feedback about this release! Your feedback is essential to make Kong better!