Skip to content

kubernetes-ingress: add activeDeadlineSeconds to crdjob configuration #381

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.

Sign up for GitHub

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

Merged
dkorunic merged 3 commits into from
Aug 28, 2026
Merged

kubernetes-ingress: add activeDeadlineSeconds to crdjob configuration #381

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
a576a0b
kubernetes-ingress: add activeDeadlineSeconds to crdjob configuration
duncan485 Aug 28, 2026
2620db9
BUILD/MINOR: kubernetes-ingress: fix trailing whitespace in crdjob va…
dkorunic Aug 28, 2026
76b836a
DOC/MINOR: kubernetes-ingress: document crdjob.activeDeadlineSeconds
dkorunic Aug 28, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions kubernetes-ingress/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -509,6 +509,7 @@ A Helm `post-install` / `pre-upgrade` hook Job that applies the controller's CRD
|---|---|---|
| `crdjob.podAnnotations` | Annotations on the Job pod. | `{}` |
| `crdjob.ttlSecondsAfterFinished` | Seconds after which the Job is garbage-collected. | `600` |
| `crdjob.activeDeadlineSeconds` | Seconds the Job may stay active before Kubernetes terminates it and marks it `DeadlineExceeded`. Omitted when unset, so the Job runs without a deadline. | _unset_ |
| `crdjob.nodeSelector` / `.tolerations` / `.affinity` | Scheduling controls for the Job pod. | `{}` / `[]` / `{}` |
| `crdjob.resources.requests` / `.limits` | CPU/memory requests and (optional) limits for the Job container. | `cpu: 250m`, `memory: 400Mi` (no limits) |

Expand Down
3 changes: 3 additions & 0 deletions kubernetes-ingress/templates/controller-crdjob.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,9 @@ metadata:
spec:
{{- if .Values.crdjob.ttlSecondsAfterFinished }}
ttlSecondsAfterFinished: {{ .Values.crdjob.ttlSecondsAfterFinished }}
{{- end }}
{{- if .Values.crdjob.activeDeadlineSeconds }}
activeDeadlineSeconds: {{ .Values.crdjob.activeDeadlineSeconds }}
{{- end }}
backoffLimit: 0
template:
Expand Down
4 changes: 4 additions & 0 deletions kubernetes-ingress/values.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -710,6 +710,10 @@ crdjob:
## ref: https://kubernetes.io/docs/concepts/workloads/controllers/ttlafterfinished/
ttlSecondsAfterFinished: 600

## Duration in seconds relative to the startTime that the job may be continuously active before the system tries to terminate it
## ref: https://kubernetes.io/docs/concepts/workloads/controllers/job/#job-termination-and-cleanup
activeDeadlineSeconds:

## Pod Node assignment
## ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/
nodeSelector: {}
Expand Down