Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

Hi team, could someone give me some guidance on how we can pass in an `envFrom` section to a `KubernetesJob` block. We want to include this using the Python API:

```          envFrom:
            - secretRef:
                name: job-secrets```

`customizations=[]`
`infra_overrides=dict()`

`#Build secret patch for job image`
`for secret in secrets_list:`
    `item = {    "op": "add",`
                `"path": "/spec/template/spec/containers/0/env/-",`
                `"value": {`
                    `"name": secret.upper(),`
                    `"valueFrom": {`
                        `"secretKeyRef": {`
                            `"name": "prefect-flow-secrets",  "key": secret.upper()`
                        `}`
                    `}`
                `}`
            `}`
    `customizations.append(item)`

`if len(customizations)&gt;0:`
   `infra_overrides['customizations'] = customizations`

then set `infra_overrides = infra_overrides` in the deployment

could this customization also be used in the `KubernetesJob.customizations` block

<https://docs.prefect.io/api-ref/prefect/infrastructure/#prefect.infrastructure.kubernetes.KubernetesJob>

not tried as our secrets list are flow specific so need to generate per deploy

gotcha. will give it a try and paste back result for reference

Another way is described here: <https://discourse.prefect.io/t/creating-and-deploying-a-custom-kubernetes-infrastructure-block/1531>

Ah this is great too. `job=KubernetesJob.job_from_file("modified_run_job.yaml")`

Thats more or less how we used to do it in prefect v1

I'm not sure adding `envFrom` via `customizations` to default template would work, since `envFrom` is not set in the default template and I think jsonpatches need the array to exist beforehand

I think you’re right. It didn’t work for me. Presumably because `envFrom` was missing

Hi <@U038DGTSA2W>
Have you found a solution to your request?
I need to do the same thing

Hey <@U02TWN4GRD0>, we decided to just do it in an external yaml like this:

```import os

from prefect.infrastructure.kubernetes import KubernetesImagePullPolicy, KubernetesJob

dir_path = os.path.dirname(os.path.realpath(__file__))

job = KubernetesJob(
    namespace="prefect",
    image_pull_policy=KubernetesImagePullPolicy.ALWAYS,
    image="xxx",
    job=KubernetesJob.job_from_file(dir_path + "/kubernetes-job-default.yaml"),
)

job.save("kubernetes-job-default", overwrite=True)```

and in the yaml, just the normal:

```      containers:
      - name: prefect-job
        image: ""
        envFrom:
          - secretRef:
              name: doppler-secrets-sett-prefect-staging```