Please add Timezone support to K8s Dashboard

[lprimak]

What would you like to be added?

I have read previous issues and saw that a decision was made at some point to display all times in UTC.
I'd like to revisit that decision because it's not user friendly.

For example, I used k8tz (https://github.com/k8tz/k8tz) to run all containers in Chicago timezone.
However, Dashboard is hardcoded to UTC and is not respecting the Container/OS timezone.

This especially confusion for Asia, as not only the time is wrong, but the day is wrong as well.

Why is this needed?

Make displayed dates / times more user-friendly and less confusing, especially in Asia.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[lprimak]

/remove-lifecycle

[lprimak]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[lprimak]

/remove-lifecycle stale