FrommyMind commented on PR #8954: URL: https://github.com/apache/seatunnel/pull/8954#issuecomment-2716642192
> current configmap is for seatunnel config. to distinguish, we need add a new configmap, that's not worth it. actually, there is a priority on java code to get timezone,which TZ > timezone > localtime, and it can be confirmed all linux distribution used as a server has /etc/localtime, and may not have TZ and /etc/timezone; my goal is sync pod timezone to k8s node, so that we must mount /etc/timezone, to prevent some zoneinfo specified in /etc/timezone are not exsit, we must mount /etc/localtime for backup; add these files to configmap, timezone sync is not automatic，if do this so，it is better to use TZ > > so if we want entirely ignore user`s environment, we can just use TZ. > > in case, this error can be easily fix by create /etc/timezone, i think this is better than other method. > > If you have any other considerations, we can discuss further In a Kubernetes cluster, we need to create this file for all nodes. I don't think this will be a good solution. -- 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: commits-unsubscr...@seatunnel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
