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.

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

Reimplement Lagoon Cronjobs with Kubernetes Cronjobs #1001

Closed
1 of 3 tasks
Schnitzel opened this issue Mar 28, 2019 · 0 comments · Fixed by #1031
Closed
1 of 3 tasks

Reimplement Lagoon Cronjobs with Kubernetes Cronjobs #1001

Schnitzel opened this issue Mar 28, 2019 · 0 comments · Fixed by #1031
Assignees

Comments

@Schnitzel
Copy link
Contributor

Schnitzel commented Mar 28, 2019

  • If the defined cronjob in .lagoon.yml is every 15mins or often: Keep the current system (injects CRONJOBS environment variable into a running pod)
  • If the defined cronjob in .lagoon.yml is less often than 15mins: reintroduce the system we had once 8ac2bd3

Additional things:

  • Update CLI Auto Idler code to check if CRONJOBS is set, if not, idle the CLI

This solves current issues:

  1. We can idle more pods (basically all cli pods for production environments) - less load on cluster
  2. this will run cronjobs for non production environments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants