GWphua commented on PR #17749: URL: https://github.com/apache/druid/pull/17749#issuecomment-2785573505
> IIUC from the changes, this shouldn't have any rolling upgrade implications, i.e. task pods launched by an Overlord where the k8sTaskPodNamePrefix was not specified can still be detected by an Overlord where this config has been specified (or an Overlord where the value of the config has been updated). @GWphua , could you please confirm if this is actually the case. Hi @kfaraz, unfortunately there will be disruptions to rolling upgrades. The old tasks (without configured `k8sTaskPodNamePrefix`) will not be detected, and Overlord will restart the on-going tasks with the configured `k8sTaskPodNamePrefix`. From the user's perspective, the web console will show the old tasks as FAILED. On our side, we need to notify our users to expect this to happen. -- 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]
