I wanted to explore whether Kubernetes timezone injection could be handled using MutatingAdmissionPolicy instead of a dedicated admission webhook.
That led me to build kube-tz, an open-source project that uses Kubernetes admission-time mutation to configure timezone data for eligible Pods.
The approach uses an init container to prepare the timezone files and supports cluster-wide defaults, per-Pod overrides, and opt-out annotations.
I'm particularly interested in feedback on a few questions:
- Is this a useful abstraction for platform teams?
- What edge cases would you want covered before running it in production?
- Are there workloads or deployment patterns where this approach would be unsuitable?
- What would you improve in the architecture?
Repository: https://github.com/kube-tz/kube-tz/
I'd appreciate honest technical feedback, including criticism of the approach.