We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi!
There is the possibility to include customization for flags:
Keda (https://keda.sh/docs/2.10/concepts/scaling-jobs/#scaledjob-spec)
Job (into ScaledJob) https://kubernetes.io/docs/concepts/workloads/controllers/job/#ttl-mechanism-for-finished-jobs
The intention is to have greater flexibility on the completion of jobs/scaleJobs and greater control related to the volumes created in cloud.
Tks!
The text was updated successfully, but these errors were encountered:
Thank you for your proposal 😄 Configuration options have been added (10daba5).
Default values are those from KEDA in their specs, to avoid any breaking change.
Is it what you thought about?
Documentation extract:
pipelines.cleanup.ttl
autoscaling.enabled
3600
pipelines.cleanup.failed
100
pipelines.cleanup.successful
Sorry, something went wrong.
Feat: New configuration options for Jobs history cleanup
10daba5
#63
Yes!!
Tks @clemlesne
clemlesne
No branches or pull requests
Hi!
There is the possibility to include customization for flags:
Keda (https://keda.sh/docs/2.10/concepts/scaling-jobs/#scaledjob-spec)
Job (into ScaledJob) https://kubernetes.io/docs/concepts/workloads/controllers/job/#ttl-mechanism-for-finished-jobs
The intention is to have greater flexibility on the completion of jobs/scaleJobs and greater control related to the volumes created in cloud.
Tks!
The text was updated successfully, but these errors were encountered: