Re: [External Email] Re: Upgrading Kafka Kraft in Kubernetes

2023-10-20 Thread Jakub Scholz
:port] upgrade > --metadata 3.6 > > This is doable using declarative Kubernetes job. > > Thank you very much, I appreciate your help. > > Jiri > > From: Jakub Scholz > Sent: Thursday, October 19, 2023 5:18 PM > To: users@kafka.apache.org > Subject: [External Email

RE: [External Email] Re: Upgrading Kafka Kraft in Kubernetes

2023-10-19 Thread Soukal , Jiří
eatures.sh --bootstrap-server [server:port] upgrade --metadata 3.6 This is doable using declarative Kubernetes job. Thank you very much, I appreciate your help. Jiri From: Jakub Scholz Sent: Thursday, October 19, 2023 5:18 PM To: users@kafka.apache.org Subject: [External Email] Re: Upgrading Kafk

Re: Upgrading Kafka Kraft in Kubernetes

2023-10-19 Thread Jakub Scholz
Hi Jiří, Why can't you run it from another Pod? You should be able to specify --bootstrap-server and point it to the brokers to connect to. You can also pass further properties to it using the --command-config option. It should be also possible to use it from the Admin API

Upgrading Kafka Kraft in Kubernetes

2023-10-19 Thread Soukal , Jiří
Hello all, Final step of the upgrade procedure is to run command like: "./bin/kafka-features.sh upgrade --metadata 3.6" In the Kubernetes world, which works in the desired state configuration (yamls and its the upper level abstractions), this is quite complicated. The first thing I tried to fin