Update KrakenD readme with the one used in PubPlatform #21801
Merged
+117
−71
Conversation
This file contains hidden or 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
AAraKKe
added
qa/skip-qa
NouemanKHAL
previously approved these changes
Oct 31, 2025
temporal-github-worker-1
bot
dismissed
NouemanKHAL’s stale review
Review from NouemanKHAL is dismissed. Related teams and files:
- agent-integrations
- krakend/images/IMAGES_README.md
alexeypilyugin
approved these changes
Oct 31, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this PR do?
Brings the README for KrakenD.
Motivation
The README was never brought to this repo because it was created through the publishing platform. This was already approved by the @DataDog/documentation team in there. This is just to make sure that the integration has a proper README for anyone that lands here.
Review checklist (to be filled by reviewers)
qa/skip-qalabel if the PR doesn't need to be tested during QA.backport/<branch-name>label to the PR and it will automatically open a backport PR once this one is merged