FrankChen021 commented on code in PR #17749: URL: https://github.com/apache/druid/pull/17749#discussion_r2027317372
########## docs/development/extensions-core/k8s-jobs.md: ########## @@ -745,6 +745,17 @@ If you are running multiple Druid clusters and would like to have a dedicated na Druid will tag Kubernetes jobs with a `druid.overlord.namespace` label. This label helps Druid filter out Kubernetes jobs belonging to other namespaces. +##### Differentiating Task Pods Created From Multiple Namespaces + +When we have task pods running in multiple namespaces, it will be difficult to tell which task pods are being started by which cluster. You can specify a task name prefix, `druid.indexer.runner.k8sTaskPodNamePrefix`, to apply your specified prefix to all task pods created by your cluster. Review Comment: ```suggestion When we have task pods started by overlords of different Druid clusters runnng in different K8S namespaces, it will be difficult to tell which task pods are being started by which overlord or Druid cluster. You can specify a task name prefix, `druid.indexer.runner.k8sTaskPodNamePrefix`, to apply your specified prefix to all task pods created by your cluster. ``` -- 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]
