Replies: 3 comments 1 reply
-
Discussed in Slack => this is a missing feature which should be added in a similar way as for Kafka brokers for example. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Raised: #9142 |
Beta Was this translation helpful? Give feedback.
1 reply
-
Adding a comment here as i always come to this issue whenever i google search this
https://strimzi.io/docs/operators/latest/deploying#proc-manual-rolling-update-strimzipodset-str |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What is the correct way to restart kafka-connect instances?
I am aware that i can restart the following in the following manner:
kafka
- annotate pods withstrimzi.io/manual-rolling-update=true
zookeeper
- annotate pods withstrimzi.io/manual-rolling-update=true
connectors
- https://github.com/strimzi/proposals/blob/main/007-restarting-kafka-connect-connectors-and-tasks.mdBut i am unsure how to effectively restart the
kafka-connect
instances as i have previously usedkubectl rollout restart deployment <connect-deployment-name>
but on occasion have observed the newer pod getting killed off by a reconcile being carried out by the operator.The main reason i am restarting the connect instances is because of outdated sidecars which need updating.
Beta Was this translation helpful? Give feedback.
All reactions