georgew5656 commented on PR #17614: URL: https://github.com/apache/druid/pull/17614#issuecomment-2590650526
> document > Thanks for the reply. I noticed that the `k8sAndWorker` was introduced in Druid 28, which means that there's no smooth migration path from MM to K8s before that. But this extension is introduced in Druid 25, can we add a note to the doc you mentioned that `k8sAndWorker` is supported since Druid 28? > > With regard to the rolling update, we have a [document](https://druid.apache.org/docs/latest/operations/rolling-updates) about it. Under the k8s-based ingestion mode, what's suggested update order? should we update overlord after historical? I think we should add some text in this doc. yep i can update those docs. in this case the update is basically several runtime props that apply to the overlord only (the other services don't change at all, the exception being the middle managers which get torn down (not really a update). my recommendation for anyone considering switching to first update to druid 28 normally (with middle managers), and then run the overlord-only update afterwards -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
