We've found that specific settings and possible even alpha features (ttlSecondsAfterFinished, specifically) are needed to make the jobs/cronjobs work well.
We likely also need some tooling (new backend for jsub or a new command)!
We've found that specific settings and possible even alpha features (ttlSecondsAfterFinished, specifically) are needed to make the jobs/cronjobs work well.
We likely also need some tooling (new backend for jsub or a new command)!
The conversation in T251027: "signatures" tool has failed job pods on Kubernetes cluster is a good touchpoint for this ticket.
Probably the most simple note here is that batch objects don't appear to be quota-able directly (just the pods they schedule), which may or may not merit controllers to do just that.
I think you are working on this @aborrero, so assigning to you to prevent duplication. Feel free to delete if you have another one.
Change 681424 had a related patch set uploaded (by Arturo Borrero Gonzalez; author: Arturo Borrero Gonzalez):
[cloud/toolforge/jobs-framework-api@main] tjf: include deployment configuration for toolsbeta kubernetes
Change 681725 had a related patch set uploaded (by Arturo Borrero Gonzalez; author: Arturo Borrero Gonzalez):
[operations/puppet@production] toolforge: nginx-ingress-jobs: specify ingress-class
Change 692633 had a related patch set uploaded (by Arturo Borrero Gonzalez; author: Arturo Borrero Gonzalez):
[cloud/toolforge/jobs-framework-api@main] jobs-framework-api: introduce initial docker image
Change 692633 merged by Arturo Borrero Gonzalez:
[cloud/toolforge/jobs-framework-api@main] jobs-framework-api: introduce initial docker image
Change 681424 merged by Arturo Borrero Gonzalez:
[cloud/toolforge/jobs-framework-api@main] jobs-framework-api: include deployment configuration for toolsbeta kubernetes
Closing this task as the design phase is mostly completed. Now moving on to the devel phase.