move data extract jobs to use k8s #36137
Conversation
| job: | ||
| environment: | ||
| TASK_NAME: IronMountainExtractTask | ||
| VAR_FV2: trigger-2 |
There was a problem hiding this comment.
does this var actually do anything for the cron trigger jobs?
| IDAM_SERVICE_HOST: https://idam-api.platform.hmcts.net | ||
| PRINTSERVICE_HOST: https://return-case-doc.ccd.platform.hmcts.net | ||
| TASK_NAME: IronMountainExtractTask | ||
| schedule: "0 5 2 * *" |
There was a problem hiding this comment.
this is 0500 every 2nd of the month? is that what we intend
There was a problem hiding this comment.
this has been updated to be 5 mins past 2am every day
the others are set to match their previous times from the orch service. This issue here came about as the old cron has 6 values not 5
There was a problem hiding this comment.
https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/#schedule-syntax is this the cron schedule type being used? if so this is 0500 every 2nd of the month was looking at the old version, ignore
| VAR_FV2: trigger-2 | ||
| useInterpodAntiAffinity: true | ||
| image: hmctspublic.azurecr.io/probate/back-office:prod-6707e09-20250109124038 #{"$imagepolicy": "flux-system:probate-back-office"} | ||
| schedule: 0 * * * * |
There was a problem hiding this comment.
if an environment doesn't override this it will run on the hour every hour?
There was a problem hiding this comment.
do we expected the env directories to ever contain anything bar these env.yaml files? if not can we have them as just env.yaml in the main directory?
…n-jobs-to-k8s' into dtspb-2859-move-cron-jobs-to-k8s
Jira link
Resolves: https://tools.hmcts.net/jira/browse/DTSPB-2859
Change description
Moving Probate data extract jobs to use k8s cron
🤖AEP PR SUMMARY🤖
I'm a bot that generates AI summaries of pull requests, see AEP for more details
Updated kustomization.yaml:
Updated demo-image-policy.yaml:
Added new files for: