Thanks Omer for answer. It helps to understand. Couple of follow up questions
1. Is there a way to confirm this using any kafka logs (message with encrypted info).
2. Is this error intermittent or happens always? Because I do see plaintext calls succeed for the same client and topic
Regards,
Nanda
-----Original Message-----
From: Ömer Şiar Baysal < osiarbaysal@gmail.com >
Sent: Thursday, May 29, 2025 1:19 PM
To: users@kafka.apache.org
Cc: rradutiu@gmail.com
Subject: Re: [EXTERNAL] Re: What config to avoid outofmemory exceptions happening in kafka server logs
Hi,
This is a known issue,
https://issues.apache.org/jira/plugins/servlet/mobile#issue/KAFKA-4493
Basically when broker receives first few bytes of the encrypted message on its plaintext listener, it may end up trying to allocate a huge buffer for the message, because it assumes the received bytes are for plaintext listener. Since encrypted message is no longer a clear text, its first 4 byte...
Posts
Hi,
This is a known issue,
https://issues.apache.org/jira/plugins/servlet/mobile#issue/KAFKA-4493
Basically when broker receives first few bytes of the encrypted message on
its plaintext listener, it may end up trying to allocate a huge buffer for
the message, because it assumes the received bytes are for plaintext
listener. Since encrypted message is no longer a clear text, its first 4
bytes can resemble anything (sometimes a huge number) thus resulting in OOM.
Hope that clears it up for you.
Ömer Şiar Baysal
On Thu, May 29, 2025, 18:18 Nanda Naga <nandanaga@microsoft.com.invalid>
wrote:
> Thanks Radu for the response.
>
> Wondering why it is out of memory? Any config to resolve this or any
> change in client to resolve this?
>
> Also, we use librdkafka client to connect to plaintext port. The memory
> errors seems intermittent as I see produces happening to plaintext as well.
>
> Regards,
> Nanda
>
> --...
Thanks Radu for the response.
Wondering why it is out of memory? Any config to resolve this or any change in client to resolve this?
Also, we use librdkafka client to connect to plaintext port. The memory errors seems intermittent as I see produces happening to plaintext as well.
Regards,
Nanda
-----Original Message-----
From: Radu Radutiu < rradutiu@gmail.com >
Sent: Wednesday, May 28, 2025 3:08 AM
To: users@kafka.apache.org
Subject: [EXTERNAL] Re: What config to avoid outofmemory exceptions happening in kafka server logs
[You don't often get email from rradutiu@gmail.com . Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
The error usually occurs when you try to connect with a client speaking TLS to the plain text port of the Kafka broker.
Radu
On Wed, May 28, 2025 at 12:37 AM Nanda Naga <nandanaga@microsoft.com.invalid>
wrote:
> I see this exception in our environment in multiple machines. What
...
The error usually occurs when you try to connect with a client speaking TLS
to the plain text port of the Kafka broker.
Radu
On Wed, May 28, 2025 at 12:37 AM Nanda Naga <nandanaga@microsoft.com.invalid>
wrote:
> I see this exception in our environment in multiple machines. What config
> will help to resolve this error?
>
> The exception I get is at
>
> java.lang.OutOfMemoryError: Unable to allocate 369295624 bytes
> at java.base/jdk.internal.misc.Unsafe.allocateMemory(Unsafe.java:632)
> at java.base/java.nio.DirectByteBuffer.<init>(DirectByteBuffer.java:125)
> at java.base/java.nio.ByteBuffer.allocateDirect(ByteBuffer.java:332)
> at java.base/sun.nio.ch.Util.getTemporaryDirectBuffer(Util.java:228)
> at java.base/sun.nio.ch.IOUtil.read(IOUtil.java:293)
> at java.base/sun.nio.ch.IOUtil.read(IOUtil.java:259)
> at java.base/sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:417)
> at
> org.apache.kafka....
Hi there,
our Kafka Streams applications occasionally show messages like the following:
[AdminClient clientId=prod.index-document-aggregator-0-admin] Skipping return offset for prod.document-20 due to error UNSTABLE_OFFSET_COMMIT.
As far as I understand, this originates from Kafka brokers rather than Kafka Streams, see ListConsumerOffsetsHandler#handleResponse ( https://github.com/apache/kafka/blob/trunk/clients/src/main/java/org/apache/kafka/clients/admin/internals/ListConsumerGroupOffsetsHandler.java ).
May someone please shed some light on this message and its implications?
Or, more specifically:
Does this imply possible data loss? (We're not using exactly_once semantics, duplicate processing would be not so much of an issue.)
Are there broker side logs or metrics that might help identify the root cause? (Replica fetcher metrics show all zeros.)
Thanks,
Karsten
I see this exception in our environment in multiple machines. What config will help to resolve this error?
The exception I get is at
java.lang.OutOfMemoryError: Unable to allocate 369295624 bytes
at java.base/jdk.internal.misc.Unsafe.allocateMemory(Unsafe.java:632)
at java.base/java.nio.DirectByteBuffer.<init>(DirectByteBuffer.java:125)
at java.base/java.nio.ByteBuffer.allocateDirect(ByteBuffer.java:332)
at java.base/sun.nio.ch.Util.getTemporaryDirectBuffer(Util.java:228)
at java.base/sun.nio.ch.IOUtil.read(IOUtil.java:293)
at java.base/sun.nio.ch.IOUtil.read(IOUtil.java:259)
at java.base/sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:417)
at org.apache.kafka.common.network.PlaintextTransportLayer.read(PlaintextTransportLayer.java:103)
at org.apache.kafka.common.network.NetworkReceive.readFrom(NetworkReceive.java:118)
at org.apache.kafka.common.network.KafkaChannel.receive(KafkaChannel.java:452)
at org.apache.kafka.common.network.KafkaChannel.read(Kafka...
Hello.
There is a weird problem where we missed almost all metrics for producers.
The Kafka server version is 2.13-3.7.1.
The JMX-exporter config is as follows:
lowercaseOutputName: true
whitelistObjectNames:
- "kafka.server:*"
- "kafka.log:*"
- "kafka.network:*"
- "kafka.controller:*"
- "kafka.security:*"
- "kafka.coordinator:*"
- "jvm.gc:*"
- "jvm.threads:*"
- "jvm.memory:*"
rules:
- pattern: ".*"
I am looking to have a metric:
"kafka.server:client-id=connector-producer-my-producer,type=Produce" : {...
However, when I try to dump what the Mbean has, I am getting nothing:
$ java -jar jmx-dump-0.12.0-standalone.jar --dump-all -p 44544 -h 127.0.0.1
| grep -c "connector-producer"
0
I am 100% sure that I have tons of consumers. However, I don't see them in
the metrics.
Can we debug why the Kafka server doesn...
On Wed, May 21, 2025 at 5:37 AM TengYao Chi < frankvicky@apache.org > wrote:
> The Apache Kafka community is pleased to announce the release for
> Apache Kafka 3.9.1
>
> This bug-fix release has several fixes, and most importantly, it adds
> Java 23 support.
>
> All of the changes in this release can be found in the release notes:
> https://www.apache.org/dist/kafka/3.9.1/RELEASE_NOTES.html
>
>
> An overview of the release can be found in our announcement blog post:
> https://kafka.apache.org/blog#apache_kafka_391_release_announcement
>
> You can download the source and binary release (Scala 2.12 / 2.13) from:
> https://kafka.apache.org/downloads#3.9.1
>
>
> ---------------------------------------------------------------------------------------------------
>
>
> Apache Kafka is a distributed streaming platform with four core APIs:
>
> ** The Producer API allows an application to publi...
Best regards, Bukhtoyarov Vladimir, Senior Java developer at vk.com https://github.com/vladimir-bukhtoyarov https://t.me/Vladimir_Bukhtoyarov
Gentle Reminder!
Regards,
Sahil
From: Sahil Sharma D
Sent: 19 May 2025 02:51 PM
To: 'Kafka Users' < users@kafka.apache.org >
Subject: RE: Inquiry About Jetty Version in Apache Kafka 4.0.0
Hi Team,
Any update on this?
Regards,
Sahil
From: Sahil Sharma D
Sent: 16 May 2025 12:35 PM
To: Kafka Users < users@kafka.apache.org <mailto: users@kafka.apache.org >>
Subject: Inquiry About Jetty Version in Apache Kafka 4.0.0
Hi Team,
I noticed that Jetty has been upgraded to version 11.x in Kafka 4.0.0. According to the Jetty website, version 11.x has already reached its end of life (EOL). Could you clarify how any future issues or CVEs related to version 11.x will be addressed?
Additionally, I would like to know if there is a plan to upgrade Jetty to version 12.x in upcoming releases.
Regards,
Sahil
The Apache Kafka community is pleased to announce the release for
Apache Kafka 3.9.1
This bug-fix release has several fixes, and most importantly, it adds
Java 23 support.
All of the changes in this release can be found in the release notes:
https://www.apache.org/dist/kafka/3.9.1/RELEASE_NOTES.html
An overview of the release can be found in our announcement blog post:
https://kafka.apache.org/blog#apache_kafka_391_release_announcement
You can download the source and binary release (Scala 2.12 / 2.13) from:
https://kafka.apache.org/downloads#3.9.1
---------------------------------------------------------------------------------------------------
Apache Kafka is a distributed streaming platform with four core APIs:
** The Producer API allows an application to publish a stream of records to
one or more Kafka topics.
** The Consumer API allows an application to subscribe to one or more
topics and process the stream of records produced to them.
** T...
hi Andy
thanks for your report. We will check it later.
Best,
Chia-Ping
Andy Li < andy@codecrafters.io > 於 2025年5月20日 週二 上午9:14寫道：
> Hi Kafka Team,
>
> I noticed a couple of response formats missing from the Kafka protocol
> guide
> < https://kafka.apache.org/protocol.html#protocol_common >:
>
> - *ApiVersions Response (Version: 4)* — Only versions 0–3 are documented,
> though version 4 of the request is included.
>
> - *DescribeTopicPartitions Response* — Not listed at all.
>
> - *Fetch Response (Version: 17)* — Only versions 4–16 are documented,
> though version 17 of the request is included.
>
> Just wanted to flag in case this was unintentional. Thanks for all the
> great work on Kafka!
>
> Best,
>
> Andy Li
>
Hi Kafka Team,
I noticed a couple of response formats missing from the Kafka protocol guide
< https://kafka.apache.org/protocol.html#protocol_common >:
- *ApiVersions Response (Version: 4)* — Only versions 0–3 are documented,
though version 4 of the request is included.
- *DescribeTopicPartitions Response* — Not listed at all.
- *Fetch Response (Version: 17)* — Only versions 4–16 are documented,
though version 17 of the request is included.
Just wanted to flag in case this was unintentional. Thanks for all the
great work on Kafka!
Best,
Andy Li
Yes, I was about to post the same. You can also directly check Jetty
version on Kafka 4.0.0 tag:
https://github.com/apache/kafka/blob/4.0.0/gradle/dependencies.gradle#L71
On Mon, May 19, 2025 at 4:57 PM Steven Schlansker
< stevenschlansker@gmail.com > wrote:
>
>
> > On May 16, 2025, at 12:04 AM, Sahil Sharma D <sahil.d.sharma@ericsson.com.INVALID> wrote:
> >
> > Hi Team,
> >
> > I noticed that Jetty has been upgraded to version 11.x in Kafka 4.0.0. According to the Jetty website, version 11.x has already reached its end of life (EOL). Could you clarify how any future issues or CVEs related to version 11.x will be addressed?
> >
> > Additionally, I would like to know if there is a plan to upgrade Jetty to version 12.x in upcoming releases.
>
> Hi Sahil, I think your premise may be mistaken - I am no authority on the project, but some searching around leads you to
> https://cwiki.apache.org/confluence...
> On May 16, 2025, at 12:04 AM, Sahil Sharma D <sahil.d.sharma@ericsson.com.INVALID> wrote:
>
> Hi Team,
>
> I noticed that Jetty has been upgraded to version 11.x in Kafka 4.0.0. According to the Jetty website, version 11.x has already reached its end of life (EOL). Could you clarify how any future issues or CVEs related to version 11.x will be addressed?
>
> Additionally, I would like to know if there is a plan to upgrade Jetty to version 12.x in upcoming releases.
Hi Sahil, I think your premise may be mistaken - I am no authority on the project, but some searching around leads you to
https://cwiki.apache.org/confluence/display/KAFKA/KIP-1032%3A+Upgrade+to+Jakarta+and+JavaEE+10+in+Kafka+4.0
which is implemented as
https://github.com/apache/kafka/pull/16754
indicating that Kafka 4 indeed already uses Jetty 12
Best,
Steven
Hi Team,
Any update on this?
Regards,
Sahil
From: Sahil Sharma D
Sent: 16 May 2025 12:35 PM
To: Kafka Users < users@kafka.apache.org >
Subject: Inquiry About Jetty Version in Apache Kafka 4.0.0
Hi Team,
I noticed that Jetty has been upgraded to version 11.x in Kafka 4.0.0. According to the Jetty website, version 11.x has already reached its end of life (EOL). Could you clarify how any future issues or CVEs related to version 11.x will be addressed?
Additionally, I would like to know if there is a plan to upgrade Jetty to version 12.x in upcoming releases.
Regards,
Sahil
This vote passes with 8 +1 votes (3 bindings) and no 0 or -1 votes.
+1 votes
PMC Members:
* Josep Prat
* Justine Olshan
* Mickael Maison
Committers:
N/A
Community:
* Paolo Patierno
* Kuan Po Tseng
* Jiunn-Yang Huang
* PoAn Yang
* Hong-Yi Chen
0 votes * No votes -1 votes * No votes Vote thread:
https://lists.apache.org/thread/5q9337moctfl6y3rdpbwcldf9bm6o1ml I'll
continue with the release process and the release announcement will follow
in the next few days. TengYao Chi
Hi All,
I am trying to have a kafka configuration where we use *OAuth2 for client
broker communication and PLAINTEXT for inter broker communication. Kafa
broker should not need to talk to the OAuth server. *
THis is what the configuration looks like:
advertised.listeners is set to SASL_PLAINTEXT and PLAINTEXT.
inter.broker.listener.name =PLAINTEXT
sasl.enabled.mechanisms=OAUTHBEARER
listener.name.sasl_plaintext.sasl.enabled.mechanisms=OAUTHBEARER
listener.name.sasl_plaintext.oauthbearer.sasl.server.callback.handler.class=org.apache.kafka.common.security.oauthbearer.OAuthBearerValidatorCallbackHandler
#listener.name.sasl_plaintext.oauthbearer.sasl.login.callback.handler.class=org.apache.kafka.common.security.oauthbearer.secured.OAuthBearerLoginCallbackHandler
#listener.name.sasl_plaintext.oauthbearer.sasl.jaas.config=org.apache.kafka.common.security.oauthbearer.OAuthBearerLoginModule
required clientId='clientId' clientSecret='clientSecret' scope='...
Hi Team,
I noticed that Jetty has been upgraded to version 11.x in Kafka 4.0.0. According to the Jetty website, version 11.x has already reached its end of life (EOL). Could you clarify how any future issues or CVEs related to version 11.x will be addressed?
Additionally, I would like to know if there is a plan to upgrade Jetty to version 12.x in upcoming releases.
Regards,
Sahil
Hi all,
Thanks for the vote so far!
Update for the system test:
1. The system tests have some failed tests:
http://jenkins.opensource4you.tw/job/kafka-e2e/317
2. The failed benchmark_test and OffsetValidationTest can pass in another
run:
https://drive.google.com/drive/folders/1lf7EH-m8PNPGfv7Fj3-FLnz_UH3un41n?usp=sharing
So the result is green.
Thanks.
Luke
On Wed, May 14, 2025 at 2:14 PM Paolo Patierno < paolo.patierno@gmail.com >
wrote:
> Hi,
> we ran all the regression tests within the Strimzi project and also all the
> KRaft migration and upgrade related test.
> Everything is fine.
>
> +1 (non binding)
>
> Thanks
> Paolo
>
> Paolo Patierno
>
> *Senior Principal Software Engineer @ Red Hat**CNCF Ambassador*
> *Microsoft MVP on **Azure*
>
> Twitter : @ppatierno < http://twitter.com/ppatierno >
> Linkedin : paolopatierno < http://it.linkedin.com/in/paolopatierno >
> GitH...
Hello Team,
I would like to setup a meeting to understand Kafka version 4 authentication issue, I am getting below error when I am doing replication from DB2 database to Kafka.
0029812: 2025-05-12T20:09:39 [TARGET_LOAD ]E: RDKAFKA - 3 - ERROR: [thrd:app]: QlikReplicate/2024.5/kafka#producer-2: 172.31.1.92:9092/1 : Connect to ipv4# 172.31.1.92:9092 failed: Unknown error (after 21014ms in state CONNECT) [1022601] (kafka_client.c:239)
00029812: 2025-05-12T20:10:00 [TARGET_LOAD ]E: RDKAFKA - 3 - ERROR: [thrd:app]: QlikReplicate/2024.5/kafka#producer-2: 172.31.1.92:9092/1 : Connect to ipv4# 172.31.1.92:9092 failed: Unknown error (after 21056ms in state CONNECT, 1 identical error(s) suppressed) [1022601] (kafka_client.c:239)
00029812: 2025-05-12T20:10:42 [TARGET_LOAD ]E: RDKAFKA - 3 - ERROR: [thrd:app]: QlikReplicate/2024.5/kafka#producer-2: 172.31.1.92:9092/1 : Connect to ipv4# 172.31.1.92:9092 failed: Unknown error (after 21028ms in state CONNECT, 2 identical er...
Hi,
we ran all the regression tests within the Strimzi project and also all the
KRaft migration and upgrade related test.
Everything is fine.
+1 (non binding)
Thanks
Paolo
Paolo Patierno
*Senior Principal Software Engineer @ Red Hat**CNCF Ambassador*
*Microsoft MVP on **Azure*
Twitter : @ppatierno < http://twitter.com/ppatierno >
Linkedin : paolopatierno < http://it.linkedin.com/in/paolopatierno >
GitHub : ppatierno < https://github.com/ppatierno >
On Mon, 12 May 2025, 10:57 TengYao Chi, < frankvicky@apache.org > wrote:
> Hello Kafka users, developers and client-developers,
>
> This is the third candidate for the release of Apache Kafka 3.9.1.
>
> This RC fixed the LICENSE-binary misalignment issue and also bump the jetty
> version for CVE-2024-13009 compared with RC1.
>
> This is a bug-fix release with several fixes, and most importantly, it adds
> Java 23 support for 3.9
>
> Release notes f...
Please let me know if you need any other details.
Get Outlook for iOS< https://aka.ms/o0ukef >
________________________________
From: Shubham Hande
Sent: Tuesday, May 13, 2025 4:13:02 PM
To: users@kafka.apache.org < users@kafka.apache.org >
Subject: Need help for Kafka version 4 authentication
Hello Team,
I would like to setup a meeting to understand Kafka version 4 authentication issue, I am getting below error when I am doing replication from DB2 database to Kafka.
0029812: 2025-05-12T20:09:39 [TARGET_LOAD ]E: RDKAFKA - 3 - ERROR: [thrd:app]: QlikReplicate/2024.5/kafka#producer-2: 172.31.1.92:9092/1 : Connect to ipv4# 172.31.1.92:9092 failed: Unknown error (after 21014ms in state CONNECT) [1022601] (kafka_client.c:239)
00029812: 2025-05-12T20:10:00 [TARGET_LOAD ]E: RDKAFKA - 3 - ERROR: [thrd:app]: QlikReplicate/2024.5/kafka#producer-2: 172.31.1.92:9092/1 : Connect to ipv4# 172.31.1.92:9092 failed: Unknown error (after 21056ms in s...
Hello Team,
I would like to setup a meeting to understand Kafka version 4 authentication issue, I am getting below error when I am doing replication from DB2 database to Kafka.
0029812: 2025-05-12T20:09:39 [TARGET_LOAD ]E: RDKAFKA - 3 - ERROR: [thrd:app]: QlikReplicate/2024.5/kafka#producer-2: 172.31.1.92:9092/1 : Connect to ipv4# 172.31.1.92:9092 failed: Unknown error (after 21014ms in state CONNECT) [1022601] (kafka_client.c:239)
00029812: 2025-05-12T20:10:00 [TARGET_LOAD ]E: RDKAFKA - 3 - ERROR: [thrd:app]: QlikReplicate/2024.5/kafka#producer-2: 172.31.1.92:9092/1 : Connect to ipv4# 172.31.1.92:9092 failed: Unknown error (after 21056ms in state CONNECT, 1 identical error(s) suppressed) [1022601] (kafka_client.c:239)
00029812: 2025-05-12T20:10:42 [TARGET_LOAD ]E: RDKAFKA - 3 - ERROR: [thrd:app]: QlikReplicate/2024.5/kafka#producer-2: 172.31.1.92:9092/1 : Connect to ipv4# 172.31.1.92:9092 failed: Unknown error (after 21028ms in state CONNECT, 2 identical er...
Re: HKT - Tender for HKSAR Digital Corporate Identity Platform - Apache Software Export Control Inquiry
Hello Rick, You may want to refer to https://www.apache.org/licenses/exports (also linked from https://security.apache.org/blog/data-processing-compliance-statements-and-sla/ ). Kind regards, Arnout Engelen ASF Security On Tue, May 13, 2025 at 8:11 AM Cheung, Rick YF via security < security@apache.org > wrote: Dear Apache Software Foundation Team, Can you review and advise the questions below? Best Regards, Rick Cheung From: Cheung, Rick YF Sent: Thursday, April 10, 2025 12:50 PM To: exports@apache.org Subject: HKT - Tender for HKSAR Digital Corporate Identity Platform - Apache Software Export Control Inquiry Dear Apache Software Foundation, This is Rick Cheung from HKT, Commercial Group, Emerging Technologies & Solutions Development team. Recently, we are bidding the tender for HKSAR Digital Corporate Identity (CorpID) Platform Development. This email serves as notification that we intend to use below ...
Re: HKT - Tender for HKSAR Digital Corporate Identity Platform - Apache Software Export Control Inquiry
Hello Rick, You may want to refer to https://www.apache.org/licenses/exports (also linked from https://security.apache.org/blog/data-processing-compliance-statements-and-sla/ ). Kind regards, Arnout Engelen ASF Security On Tue, May 13, 2025 at 8:11 AM Cheung, Rick YF via security < security@apache.org > wrote: Dear Apache Software Foundation Team, Can you review and advise the questions below? Best Regards, Rick Cheung From: Cheung, Rick YF Sent: Thursday, April 10, 2025 12:50 PM To: exports@apache.org Subject: HKT - Tender for HKSAR Digital Corporate Identity Platform - Apache Software Export Control Inquiry Dear Apache Software Foundation, This is Rick Cheung from HKT, Commercial Group, Emerging Technologies & Solutions Development team. Recently, we are bidding the tender for HKSAR Digital Corporate Identity (CorpID) Platform Development. This email serves as notification that we intend to use below ...
Hi, we are setting up client metrics collection for our system according to KIP-714
We maintain one centralized metrics collection endpoint for multiple clusters and create dashboards to select the cluster of interest by metric label.
For "normal" metrics that we report ourselves we are easily able to attach a "cluster=test", "cluster=qa", or "cluster=prod" label to drive this behavior.
For broker metrics, we wrote a MetricsReporter implementation which has an opportunity to attach tags from the process environment to the broker metrics.
For consumer, producer, and Streams metrics, this seems to not be possible:
The client configuration does not seem to allow attaching an additional tag.
The broker configuration also does not seem to allow attaching an additional tag.
The ClientTelemetry reporter interface only provides you packed byte[] data, which is extremely inconvenient to unpack, rewrite, and repack.
Is there an easy way to ac...
Hello Kafka users, developers and client-developers,
This is the third candidate for the release of Apache Kafka 3.9.1.
This RC fixed the LICENSE-binary misalignment issue and also bump the jetty
version for CVE-2024-13009 compared with RC1.
This is a bug-fix release with several fixes, and most importantly, it adds
Java 23 support for 3.9
Release notes for the 3.9.1 release:
https://dist.apache.org/repos/dist/dev/kafka/3.9.1-rc2/RELEASE_NOTES.html
Please download, test, and vote by *Sunday, May 18, 9:00 AM PT*
Kafka's KEYS file containing PGP keys we use to sign the release:
https://kafka.apache.org/KEYS
* Release artifacts to be voted upon (source and binary):
https://dist.apache.org/repos/dist/dev/kafka/3.9.1-rc2/
* Docker release artifacts to be voted upon:
apache/kafka:3.9.1-rc2:
https://hub.docker.com/layers/apache/kafka/3.9.1-rc2/images/sha256-5862db4a63a6dd7d46fd14771b10a1b39e069c2c47f17d8e4640f960720a0ead
apache/kafka-native:3.9.1-rc2:...
Hi,
I am trying out ZK to kraft migration in our k8s environment. So for the
initial step, that is to deploy Kraft controller with migration, I have
deployed 3 Kraft controller vai this statefulset:
# {% raw %}
kind: StatefulSet
apiVersion: apps/v1
metadata:
name: kraft-controller
namespace: "cgbu-ums-dev"
labels:
application: osdmc
component: kraft-controller
spec:
updateStrategy:
type: RollingUpdate
serviceName: kraft-controller
podManagementPolicy: "Parallel"
replicas: 3
selector:
matchLabels:
application: osdmc
component: kraft-controller
template:
metadata:
labels:
application: osdmc
component: kraft-controller
version: '3.9'
occloud.oracle.com/open-network-policy : allow
spec:
nodeSelector:
occloud.oracle.com/nodeGroup : cgbu-ums-dev
terminationGracePeriodSeconds: 300
containers:
- name: kraft-...