@Marvin When I try to create a dev worker for my dev work pool on prefect, and attempt to helm install, I get this error: Error: INSTALLATION FAILED: values don't meet the specifications of the schema(s) in the following chart(s): prefect-worker: - worker: Additional property serviceAccount is not allowed - worker: Additional property fullnameOverride is not allowed How can I add a second worker for a dev work pool environment. I am following the steps as outlined here: https://github.com/PrefectHQ/prefect-helm/tree/main/charts/prefect-worker How can I resolve this error and get two workers on the same service account?

The error messages you're encountering when trying to install a second worker using Helm are due to some properties being included in your configuration that are not permitted according to the Prefect Helm chart's schema. ### Causes of the Error: 1.

serviceAccount

and

fullnameOverride

are being flagged as "Additional property not allowed". This typically means that the values you've specified for these properties are not recognized by the schema defined in the Helm chart. ### How to Resolve: 1. Remove Unsupported Properties: Double-check the Helm chart's documentation for the correct properties allowed under

worker

. As per your error,

serviceAccount

and

fullnameOverride

are not allowed. Check the values.yaml file in the Helm chart repository. Ensure that the properties you're including are supported. 2. Service Account Configuration: If you need to use a specific service account for your workers, it should be configured correctly according to the documented properties. You may likely need to reference predefined service accounts rather than attempting to set configurations that the chart doesn't support. ### Steps: 1. Review the values.yaml: Verify the properties allowed under

worker

. 2. Correct Configuration File: - Remove or correct the

fullnameOverride

and

serviceAccount

entries if they are not supported. - Define the service account and any related configuration using allowed properties. ### Example: Replace the unsupported

serviceAccount

and

fullnameOverride

with properties from the Helm chart documentation:

yaml
worker:
  name: your-worker-name
  workQueue: your-work-queue
  # Ensure the following values match the allowed schema
  # Example allowed configuration
  env:
    - name: PREFECT_API_URL
      value: your-prefect-api-url
    - name: PREFECT_API_KEY
      value: your-prefect-api-key
  # Consider looking into 'podSecurityContext' or other helm chart values

If you need to create multiple workers under the same service account, use the correct support properties and structure. For further customization, such as assigning the workers to a specific Kubernetes Service Account, you might need to look at the Helm chart's RBAC section or refer to how the worker's role bindings and service accounts are meant to be configured. ### Documentation & Reference Links: 1. Service Account in Prefect 2.x: https://docs-2.prefect.io/latest/cloud/users/service-accounts/ 2. Service Account in Prefect 3.x: https://docs-3.prefect.io/3.0/manage/cloud/manage-users/service-accounts/ 3. Prefect Helm: https://github.com/PrefectHQ/prefect-helm/tree/main/charts/prefect-worker If you're still having issues after ensuring that your configuration aligns with Helm chart standards, consider reaching out for support in the Prefect community or opening an issue in the GitHub repo for a more technical dive into your specific configuration.