Hello everyone! We are using `datahub-ingestion-cr...
# all-things-deployment
l
Hello everyone! We are using
datahub-ingestion-cron
in values.yaml to run 5 ingestion crons. One thing is, we have common
env
and
envFromSecrets
across all 5 ingestions. For now, I’m writing all these env variables in every cron jobs each. Is there a way to avoid this duplication and write it once? (something like datahub-frontend’s extraEnvs?)
Copy code
datahub-ingestion-cron:
  enabled: true
  image:
    repository: ...
    tag: ...
  crons:
    cron-1: ...
      env:                      --> same as cron-2
        common-env: ...
      envFromSecrets:
        common-env-secrets: ...
    cron-2: ...
      env:
        common-env: ...
      envFromSecrets:
        common-env-secrets: ...
1
s
Hi, it looks like such feature is not available as on today when I look at the way cronJobs are rendered here. But I agree with you it is worth supporting some common env/secrets and possibly overriding them in cronJob specific configs. I also miss
podSecurityContext
configuration in the cronJobs generated.