Skip to content

feat: render nodeSelector in the housekeeping clean-harvester-logs cronjob - #241

Merged
edevosc2c merged 2 commits into
mainfrom
housekeeping-cronjob-nodeselector
Oct 1, 2026
Merged

edevosc2c merged 2 commits into
mainfrom
housekeeping-cronjob-nodeselector

Conversation

@edevosc2c

Copy link
Copy Markdown
Member

Summary

The geonetwork/housekeeping/clean-harvester-logs CronJob renders housekeeping.tolerations but no nodeSelector, so unlike the rest of the instance it cannot be pinned to the nodes selected via the global georchestra.nodeSelector value (in our setup the geOrchestra nodes are tainted, and the job drifted onto non-geOrchestra workers).

This mirrors the pattern already used by extra/cronjob-fix-permissions-pvc.yaml:

nodeSelector:
  "kubernetes.io/os": linux
  {{- with .Values.georchestra.nodeSelector }}
  {{- toYaml . | nindent 12 }}
  {{- end }}

With georchestra.nodeSelector already set in our values, the cronjob lands on the same nodes as the other webapps with no further configuration.

Second commit bumps the chart version to 1.20.0.

Testing

  • helm lint clean
  • helm template with values setting georchestra.nodeSelector: {app: georchestra} renders the selector into the job pod spec
  • rendered CronJob passes kubectl create --dry-run=client schema validation

…onjob

Follows the pattern used by the fix-permissions-pvc cronjob: merges the
global georchestra.nodeSelector values into the job pod spec, so the
cronjob can be pinned to the same nodes as the rest of the instance.
@edevosc2c
edevosc2c merged commit a7194e3 into main Oct 1, 2026
1 check 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.

1 participant