Redpanda also works with Mimir

[meticulo3366]

What this PR does

Which issue(s) this PR fixes or relates to

Fixes #

Checklist

• Tests updated.
• Documentation added.
• CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX]. If changelog entry is not needed, please add the changelog-not-needed label to the PR.
• about-versioning.md updated with experimental features.

---

Note

Updates Kafka backend docs to add Redpanda (uses defaults with example link) and clarify Warpstream flag, keeping Apache/Confluent as default setups.

• Docs (Kafka backend configuration):
  • Add guidance for Redpanda (uses default options) with a working example link.
  • Clarify Warpstream setup by specifying -ingest-storage.kafka.use-compressed-bytes-as-fetch-max-bytes=false.
  • Keep Apache Kafka and Confluent Kafka noted as requiring no additional config.
  • Remove duplicate Warpstream section and organize backend variants.

^{Written by Cursor Bugbot for commit 2882b41. This will update automatically on new commits. Configure here.}

[CLAassistant]

All committers have signed the CLA.

[meticulo3366]

i love grafana, excited to add to the ecosystem

[dimitarvdimitrov]

amazing!! Thanks for contributing that!

I'm not sure if the section on redpanda isn't too marketing-inclined, but I'll leave @tacole02 weigh in on that one

[tacole02]

Thank you for contributing this! Overall this looks good. I left a few comments and suggestions.

[cursor]

Bug: YAML frontmatter accidentally removed from documentation

The YAML frontmatter containing aliases, description, menuTitle, title, and weight fields was removed from the documentation file. This metadata is essential for the documentation system to generate proper navigation, SEO metadata, and URL aliases. Other files in docs/sources/mimir/configure/ retain this frontmatter, and a reviewer has requested its restoration.

docs/sources/mimir/configure/configure-kafka-backend.md#L1-L8

mimir/docs/sources/mimir/configure/configure-kafka-backend.md

Lines 1 to 8 in 7b9e098

	# Configure the Grafana Mimir Kafka backend
	Grafana Mimir supports using Kafka as the first layer of ingestion in the ingest storage architecture. This configuration allows for scalable, decoupled ingestion that separates write and read paths to improve performance and resilience.
	Starting with Grafana Mimir 3.0, ingest storage is the preferred and stable architecture for running Grafana Mimir.
	## Configure ingest storage

 

---

[56quarters]

This copy feels a little too much like marketing. Could you please limit the section for Red Panda to the same information as other Kafka implementations?

[meticulo3366]

@tacole02 I just incorporated all of your feedback, can you merge in please 🙏 ?

[meticulo3366]

I incorpoarted all the changes and simplified the document, please merge in

[56quarters]

Thank you. Could you please move the Warpstream and Redpanda blocks to keep them in alphabetical order? Otherwise LGTM