@Marvin I’ve deployed the Prefect to EKS using latest helm charts. The Work Pool is configured to launch jobs to “default” namespace. I found how to change it in the console. But is there a way I can set in the values file? Thanks!

To set the namespace for the work pool in the values file when deploying Prefect to EKS using Helm charts, you can customize the Helm values by adding the

namespace

field in the job configuration section. Here is an example configuration snippet for the

values.yaml

file:

worker:
  job:
    namespace: "your-namespace"

Replace

"your-namespace"

with your desired namespace. For more detailed configurations and examples, you can refer to the Prefect Kubernetes (Worker) documentation: https://docs.prefect.io/latest/integrations/prefect-kubernetes/worker/ Additionally, more details on deploying with Helm can be found here: https://docs.prefect.io/latest/guides/deployment/kubernetes/ If you encounter any issues, searching through Prefect's GitHub repository can provide additional context and examples: https://github.com/PrefectHQ/prefect/issues I hope this helps in configuring your Prefect deployment on EKS!

@Marvin not sure it is a correct solution. Based on docs we can override configs of the Work Pool with deployment configs? But I would love just to make it for Work Pool in helm values. Do I need to provide a base job template there?

It seems you're right. To override or set specific configurations for a Work Pool, such as the namespace, within a Helm values file, you need to provide a base job template. This template will define the job configuration and the needed parameters. Here's a summary of the steps and an example configuration: 1. Define the Base Job Template: The base job template should be included in your

values.yaml

file. This template will specify the job configuration and use placeholders to reference values. 2. Include Job Configuration in Helm Values: Add the base job template in the Helm

values.yaml

file, specifying the namespace or any other configurations. Example `values.yaml`:

worker:
  jobTemplate:
    apiVersion: batch/v1
    kind: Job
    metadata:
      namespace: "{{ default .Values.worker.namespace 'default' }}"
      labels:
        app: prefect-job
    spec:
      template:
        spec:
          containers:
            - name: prefect-job
              image: "{{ .Values.worker.image }}"
              env: "{{ .Values.worker.env }}"
              args: "{{ .Values.worker.command }}"
              resources:
                requests:
                  memory: "{{ .Values.worker.memoryRequest }}"
                  cpu: "{{ .Values.worker.cpuRequest }}"
              imagePullPolicy: "{{ .Values.worker.imagePullPolicy }}"
          restartPolicy: Never
  namespace: "your-namespace"
  image: "prefecthq/prefect:latest"
  env: []
  command: []
  memoryRequest: "256Mi"
  cpuRequest: "500m"
  imagePullPolicy: "IfNotPresent"

In the above configuration: - The

namespace

field in the job template is set to a dynamic value using placeholders. - The

namespace

variable is defined in the values file as

"your-namespace"

. For further customization and detailed steps, refer to the Prefect Work Pools documentation and the Kubernetes Worker documentation. Hope this helps streamline your deployment configuration!