krishvishal opened a new issue, #4519: URL: https://github.com/apache/iggy/issues/4519
## Summary Metadata sends a null cluster id, and DescribeCluster (60) is not served. Java Admin falls back to Metadata, so most tools see a null id. Who hits it: - Confluent REST Proxy throws `UnsupportedProtocolException`, so every v3 endpoint fails. Confluent for Kubernetes manages topics through that API. - Schema Registry serdes in confluent-kafka-javascript 1.11, with the ASSOCIATED strategy, fail every send. - `kafka-cluster cluster-id` prints "No cluster ID found". Connect, Spring, kminion and Datadog log or label a null id. ## Scope - [ ] Create one stable id, and store it in Iggy - [ ] Return it in Metadata v2+ and in DescribeCluster v0-2 - [ ] Never change it. Kafka 4.4 clients send it back in ApiVersions v5 (KIP-1242) ## Acceptance criteria - [ ] `kafka-cluster cluster-id` prints the same id before and after a gateway restart - [ ] Confluent REST Proxy v3 lists the cluster ## References - REST Proxy: [ClusterManagerImpl.java](https://github.com/confluentinc/kafka-rest/blob/0d30749e53e54ec0ad52f0532c9fad43de6b95c6/kafka-rest/src/main/java/io/confluent/kafkarest/controllers/ClusterManagerImpl.java) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
