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
pgbench jobs are not cleaned by default. It would be great to have to possibility to clean them automatically after a certain time.
The ttlSecondsAfterFinished option of a Kubernetes Job could be implemented. See https://kubernetes.io/docs/concepts/workloads/controllers/job/#clean-up-finished-jobs-automatically
It could be configured in the YAML file, in a job or pgbench / section . For example for one hour TTL :
apiVersion: postgresql.cnpg.io/v1 kind: Cluster metadata: name: perf-cluster spec: imageName: ghcr.io/cloudnative-pg/postgresql:16.2 instances: 1 pgbench: ttlSecondsAfterFinished: '3600' ...
By default, we can keep it disabled.
It could be done as a parameter given at the pgbench plugin. kubectl cnpg pgbench --ttl 300 .....
kubectl cnpg pgbench --ttl 300 .....
No response
No
Yes
The text was updated successfully, but these errors were encountered:
gbartolini
Successfully merging a pull request may close this issue.
Is there an existing issue already for this feature request/idea?
What problem is this feature going to solve? Why should it be added?
pgbench jobs are not cleaned by default. It would be great to have to possibility to clean them automatically after a certain time.
Describe the solution you'd like
The ttlSecondsAfterFinished option of a Kubernetes Job could be implemented. See https://kubernetes.io/docs/concepts/workloads/controllers/job/#clean-up-finished-jobs-automatically
It could be configured in the YAML file, in a job or pgbench / section . For example for one hour TTL :
By default, we can keep it disabled.
Describe alternatives you've considered
It could be done as a parameter given at the pgbench plugin.
kubectl cnpg pgbench --ttl 300 .....
Additional context
No response
Backport?
No
Are you willing to actively contribute to this feature?
Yes
Code of Conduct
The text was updated successfully, but these errors were encountered: