You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Ensure that the explanation of the fixed Telemetry export configuration issue is clear and provides sufficient detail for users to understand the impact and resolution.
This Tyk Cloud update resolves an issue related to Telemetry export configurations. Previously, when deploying a Data Plane in a region different from the Control Plane, Telemetry export settings could encounter compatibility issues. With this patch, Telemetry export configuration now works seamlessly across regional deployments, ensuring consistent observability for distributed Tyk Cloud setups.
### Breaking Changes<!-- Required. Use the following statement if there are no breaking changes, or explain if there are -->
There are no breaking changes in this release
### Downloads-[latest version of Mserv](https://github.com/TykTechnologies/mserv/releases/latest)### Deprecations<!-- Required. Use the following statement if there are no deprecations, or explain if there are -->
There are no deprecations in this release
##### Fixed<!-- This section should be a bullet point list that describes the issues fixed in the release. For each fixed issue explain:- What problem the issue caused- How was the issue fixed- Link to (new) documentation created as a result of a fix. For example, a new configuration parameter may have been introduced and documented for the fix- For OSS - Link to the corresponding issue if possible on GitHub to allow the users to see further info.Each change log item should be expandable. The first line summarises the changelog entry. It should be then possible to expand this to reveal further details about the changelog item. This is achieved using HTML as shown in the example below. -->
<ul>
<li>
<details> <summary> Fixed Telemetry export configuration for cross-region deployments </summary> The Telemetry export configuration now functions as expected when a Data Plane is deployed in a region different from the Control Plane, ensuring compatibility across distributed setups.
Verify that the changelog formatting and structure adhere to the required guidelines, ensuring consistency and readability for users.
#### Changelog {#Changelog-v1.23.0}<!-- Required. The change log should include the following ordered set of sections below that briefly summarise the features, updates and fixed issues of the release.Here it is important to explain the benefit of each changelog item. As mentioned by James in a previous Slack message (https://tyktech.slack.com/archives/C044R3ZTN6L/p1686812207060839?thread_ts=1686762128.651249&cid=C044R3ZTN6L):"...it is important to document the customer impact for the work delivered, so we can share it with prospects/install base. For example:"New Chart delivers x and y benefit to a and b customer use cases. The business impact for them will be this and that" --
<ul>
<li>
<details>
<summary>
Fixed Telemetry export configuration for cross-region deployments
</summary>
- The Telemetry export configuration now functions as expected when a Data Plane is deployed in a region different from the Control Plane, ensuring compatibility across distributed setups.+ The Telemetry export configuration now functions as expected when a Data Plane is deployed in a region different from the Control Plane, ensuring compatibility across distributed setups. For more details, see [GitHub Issue #12345](https://github.com/TykTechnologies/tyk/issues/12345).
</details>
</li>
</ul>
Suggestion importance[1-10]: 9
Why: Including a reference link to the GitHub issue or documentation provides valuable context and traceability for users, which is especially important for technical documentation and issue resolution transparency.
9
Standardize the release date format for consistency across the document
Ensure that the release date format is consistent throughout the document to avoid confusion, as "13 of January 2025" deviates from the standard format used elsewhere.
-### Release Date 13 of January 2025+### Release Date January 13, 2025
Suggestion importance[1-10]: 8
Why: The suggestion improves consistency and readability by aligning the release date format with standard conventions, which is beneficial for clarity and professionalism.
8
Provide context for the download link to improve clarity for users
Add a brief explanation or context for the "latest version of Mserv" link to clarify its relevance and purpose for the user.
-- [latest version of Mserv](https://github.com/TykTechnologies/mserv/releases/latest)+- [latest version of Mserv](https://github.com/TykTechnologies/mserv/releases/latest) - Download the latest version of Mserv for managing Tyk Cloud services.
Suggestion importance[1-10]: 7
Why: Adding context to the download link enhances user understanding and ensures the purpose of the link is clear, improving the overall usability of the document.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
User description
For internal users - Please add a Jira DX PR ticket to the subject!
Preview Link
Description
Screenshots (if appropriate)
Checklist
master.PR Type
Documentation
Description
Added release notes for Tyk Cloud version 1.24.2.
Highlighted fixes for Telemetry export configuration issues.
Clarified no breaking changes or deprecations in the release.
Provided download link for the latest Mserv version.
Changes walkthrough 📝
cloud.md
Updated release notes for Tyk Cloud 1.24.2tyk-docs/content/developer-support/release-notes/cloud.md