Skip to content

Conversation

@oded7hoffman
Copy link
Contributor

Description

Adding requests and limits to Konnector jobs

Motivation and Context

We want to uphold the highest standards, and adding requests and limits for the different workloads is a step in the right direction.

  • New feature (non-breaking change which adds functionality)

batch:
backoffLimit: 4 # Maximum number of retries before the job is considered failed. After 4 attempts, the job will fail.
ttlSecondsAfterFinished: 3600 # Time-to-live for completed jobs, jobs will be automatically deleted 3600 seconds (1 hour) after completion
cleanupJob:
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we want to think about the backOffLimit and the ttlinSeconds? isn't it related to cleaning up jobs ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nwolfin This is for the installer konnector job, not the cleanup job. And I don't think we need backOffLimit for it. (Currently, we remove it once it's finished, so ttlSecondsAfterFinished doesn't make any sense.)

@yishaynaPalo yishaynaPalo requested a review from nwolfin January 4, 2026 17:08
@yishaynaPalo yishaynaPalo merged commit d0f7d7b into release/cloud-1.4 Jan 4, 2026
2 checks passed
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

Successfully merging this pull request may close these issues.

4 participants