Skip to content

Watcher per deployment #808

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

Open
shane-davidson opened this issue Apr 7, 2025 · 2 comments
Open

Watcher per deployment #808

shane-davidson opened this issue Apr 7, 2025 · 2 comments

Comments

@shane-davidson
Copy link

Currently Keel watches each image and register the polling schedule against the first registered container image.

We have multiple deployments with the same image that need to be restarted at different times.

Is this something that is possible to do with Keel?

@david-garcia-garcia
Copy link
Collaborator

When in polling mode, being able to control deployment schedules is a very relevant use case. @shane-davidson if willing to contribute, this could be achieved by introducing new annotations to constraint when images are deployed:

keel.sh/updateScheduleCronTab: 0 6,12 * * *
keel.sh/updateScheduleDuration: 5m
keel.sh/updateScheduleCoolDown: 30m

Where:

  • cronTab: when the disruption/deployment windows start
  • duration: because crontab itself does not allow to declar windows, the length of the deployment window
  • coolDown: do not update an image/deployment if it was already updated in the last coolDown time frame

In terms of implementation, we don't really need to manage schedules at all, simply check if we are inside a valid updateSchedule.

@david-garcia-garcia
Copy link
Collaborator

Should be fixed by:

#814

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

No branches or pull requests

2 participants