I want to upgrade kafka to version 4.0.0, do you support this?

[anhnch30820]

Apache Kafka has reported a security vulnerability called CVE-2025-27817. So I tried changing the tag of kafka to 4.0.0 but got an error related to kafka configuration.

[haorenfsa]

kafka v4 is a fairly new version. I'm not very sure about this. Just searched for it, and I found it may require a couple of steps:

3.x => 3.9 => ZK to KR migration => 4.0

https://www.openlogic.com/blog/upgrade-kafka-4-planning#kafka-4-migration-and-upgrade-considerations

[anhnch30820]

@haorenfsa I want to use network policy in K8s to limit kafka access. Is this a temporary solution to this problem without updating the config milvus?

[haorenfsa]

Is this a temporary solution to this problem without updating the config milvus?

@anhnch30820 I'm not sure you mean for use network policy in K8s to limit kafka access. or for upgrade kafka to version 4.0.0.

If for the front one, you don't need make any changes as long as you still let milvus pod to access kafka.

If for the latter one, one simple solution I can think of now, is to use the backup & restore procedure.

1. deploy a kafka v4.0
2. start a new milvus setting mq to that kafka
3. call old milvus flushall api to make sure all data in kafka gets consumed by milvus.
4. stop old milvus
5. make a backup for old milvus
6. restore the backup data on that new milvus

https://github.com/zilliztech/milvus-backup