Limits of Enabling NodeLocalTimeZone by Default in k3s

The goal is to decide whether k3s should enable the NodeLocalTimeZone feature gate by default, allowing pods to inherit the host’s time zone settings.

As of k3s v1.23.0+k3s1 the feature gate exists but is disabled, leaving containers in UTC unless explicitly turned on. Enabling it simplifies time‑sensitive workloads but raises concerns about security, multi‑tenancy, and the need to restart pods when the host time zone changes.

What trade‑offs should guide the default setting, how can potential risks be mitigated, and what communication strategy would best inform users of any change?