-
Notifications
You must be signed in to change notification settings - Fork 26
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
jobs should be deleted and recreated if new values are made #138
Comments
It isn't possible without replacing the whole job. I looked it up again to confirm https://serverfault.com/questions/809632/is-it-possible-to-rerun-kubernetes-job |
Thanks. What I mean is we should have a mechanism of some sort that deletes and recreates jobs, not necessarily literally restart the exact job again. We do this with xtz-shots. |
this may be possible with deleteBeforeReplace on the job https://www.pulumi.com/docs/concepts/options/deletebeforereplace/#:~:text=Resource%20option%3A%20deleteBeforeReplace&text=By%20default%2C%20to%20minimize%20downtime,resource%20before%20creating%20its%20replacement. |
We made changes to the rollup node values f58b3cf and the actdivation job did not clear out and restart causing us to manually have to delete and create a new job on the cluster.
Expected functionality should be if a job is dependent on a value it should be deleted and restarted to prevent this manual intervention.
The text was updated successfully, but these errors were encountered: