I'm attempting to use the helm chart to deploy Dagster but I keep getting the example user code instead of my code even though I updated the dagster-user-deployments section with my user code image. Am I missing a configuration in values.yaml?

dagster-user-deployments:
  # Creates a workspace file with the gRPC servers hosting your user code.
  enabled: true

  # If you plan on deploying user code in a separate Helm release, set this to false.
  enableSubchart: true

  # List of unique deployments
  deployments:
    - name: "dagster-code"
      image:
        repository: "<http://repo.azurecr.io/dagster-code|repo.azurecr.io/dagster-code>"
        tag: latest
        # Change with caution! If you're using a fixed tag for pipeline run images, changing the
        # image pull policy to anything other than "Always" will use a cached/stale image, which is
        # almost certainly not what you want.
        pullPolicy: Always
      # Arguments to `dagster api grpc`.
      # Ex: "dagster api grpc -m dagster_test.test_project.test_pipelines.repo -a define_demo_execution_repo"
      # would translate to:
      # dagsterApiGrpcArgs:
      #   - "-m"
      #   - "dagster_test.test_project.test_pipelines.repo"
      #   - "-a"
      #   - "define_demo_execution_repo"
      dagsterApiGrpcArgs:
        - "-f"
        - "/opt/dagster/app/repository.py"
      port: 3030

are you trying to upgrade an existing helm deployment or deploying one from scratch using your custom image?

deploy from scratch

is there any way the

dagster-code

image could have the example files rather than your own?

no, also the pod name doesn't reference my name provided in values.yaml

@Jeff Hulbert did you update your repository index?

did that ~1 day ago, will give it a try

sanity check with helm search repo that 0.11.0 is present

confirmed 0.11.0

oh nice, and you supply that instead of the

dagsterApiGrpcArgs

?

local testing, didn't change the way values.yaml is setup