Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

A user's cronjob is getting scheduled for a time in the past #4920

Closed
5 tasks
jaskaransarkaria opened this issue Oct 27, 2023 · 1 comment
Closed
5 tasks

A user's cronjob is getting scheduled for a time in the past #4920

jaskaransarkaria opened this issue Oct 27, 2023 · 1 comment
Assignees
@jaskaransarkaria
Labels
Environments support-team

Comments

@jaskaransarkaria
Copy link
Contributor

Background

A user has a cronjobs reporting that they are long-running. I suspect this is because k8s API hasn't got a timezone adjusted time, so times are an hour behind, however, Prometheus is time zone adjusted so prometheus alerts that the job is long-running as it is time zone adjusted.

https://mojdt.slack.com/archives/C57UPMZLY/p1696839800256199

Approach

Add a timezone file to kube-state-metrics kubernetes/kube-state-metrics#500 (comment)

Definition of done

  • readme has been updated
  • user docs have been updated
  • another team member has reviewed
  • smoke tests are green
  • prepare demo for the team

Reference

How to write good user stories
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jaskaransarkaria jaskaransarkaria

Labels
Environments support-team
Projects
Cloud Platform
Archived in project
Milestone
No milestone
Development

No branches or pull requests
4 participants
@davidkelliott @jaskaransarkaria @poornima-krishnasamy @sj-williams