Tyk MDCB v2.6 Release Notes

Last updated: 3 minutes read.

Licensed Protected Product

This page contains all release notes for version 2.6 displayed in reverse chronological order

Support Lifetime

Our minor releases are supported until our next minor comes out.

2.6.0 Release Notes

Release date 2 July 2024

Breaking Changes

This release has no breaking changes.

3rd Party Dependencies & Tools

Third Party Dependency Tested Versions Compatible Versions Comments
Redis 6.2.x, 7.x 6.2.x, 7.x Used by MDCB
MongoDB 5.0.x, 6.0.x, 7.0.x 4.4.x, 5.0.x, 6.0.x, 7.0.x Used by MDCB
PostgreSQL 12.x - 16.x LTS 12.x - 16.x Used by MDCB

Given the time difference between your upgrade and the release of this version, we recommend customers verify the ongoing support of third-party dependencies they install, as their status may have changed since the release.

Deprecations

Starting with MDCB v2.6.0, the configuration parameter http_port has been introduced to replace the original healthcheck_port. This new HTTP port is designed to expose various endpoints for monitoring and debugging MDCB.

Changes in MDCB v2.6.0:
  • New Configuration: http_port is the new parameter for defining the HTTP port, with a default value of 8181.
  • Deprecation: The healthcheck_port parameter is deprecated and will no longer be used in future MDCB versions.
  • Helm Chart Update: The MDCB Helm chart now includes the option mdcb.probes.httpPort, which takes precedence over mdcb.probes.healthcheckPort. For consistency and future compatibility, it is recommended to use mdcb.probes.httpPort.
Backward compatibility:

The http_port parameter is backward compatible, meaning it will function correctly with all existing MDCB versions, ensuring a smooth transition.

Recommendations for users:
  • Update Configurations: Modify your MDCB configurations to use the new http_port parameter.

Upgrade instructions

If you are using a 2.5.x version, we advise you to upgrade ASAP to this latest release. If you are on an older version, you should skip 2.5.0 and upgrade directly to this release.

Release Highlights

Tyk v5.4 Compatibility

MDCB 2.6.0 is an update for compatibility for synchronisation with Tyk v5.4 API Definitions.

Comprehensive Data Plane Node Information

MDCB 2.6 introduces a new /dataplanes endpoint that provides a comprehensive view of all data plane nodes connected to MDCB, including crucial metadata and status information for each node. The admin secret is required in the header to access these information.

Please refer to the changelog below.

Downloads

Changelog

Security

The following CVEs have been resolved in this release:

Fixed
  • Fixed MDCB failure when Tyk Dashboard is upgraded from v4 to v5 Fixed a bug where upgrading Tyk Dashboard from version 4 to version 5 caused an MDCB failure when using the default PostgreSQL protocol. Resolved the issue in MDCB by detecting cached plan errors, then reconnecting to the storage and rerunning the query to ensure proper functionality.
Added
  • Retrieve information of all the connected data plane nodes Adding a `/dataplanes` endpoint that offers a comprehensive view of all data plane nodes connected to MDCB. This endpoint provides crucial metadata and status information for each connected node, enabling efficient monitoring and troubleshooting. It requires an administrative key provided in the `x-tyk-authorization` header for access, ensuring secure and controlled usage. Successful requests return an array of node details, including node ID, API key, group ID, version, TTL, tags, health status, API statistics, and host details.
Updated
  • Update for compatibility with API definitions for Tyk v5.4

    MDCB 2.6.0 supports Tyk API definitions up to Tyk Gateway v5.4.0. Please use MDCB 2.6.x with Tyk Gateway v5.4.0+.

  • Updated to Go 1.22

    MDCB has been updated to use Go 1.22 to benefit from fixed security issues, linkers, compilers etc.


Further Information

Upgrading Tyk

Please refer to the upgrading Tyk page for further guidance with respect to the upgrade strategy.

FAQ

Please visit our Developer Support page for further information relating to reporting bugs, upgrading Tyk, technical support and how to contribute.