Hello, I'm working with the k8s-example, default a...
# deployment-kubernetes
j
Hello, I'm working with the k8s-example, default architecture... Just doing general test to make sure I'm comfortable deploying and understanding the setup. For
useer code deployment
within the
values.yaml
file if I wanted another repo (or workspace) do I just duplicate under "userDeployment" and change the repo name? Do I also need to change "port" for every new deployment? The below only seems to create a pod for
k8s-example-user-code-2
I was hoping this would create two repos just the containing the same content
Copy code
userDeployments:
  enabled: true
  deployments:
    - name: "k8s-example-user-code-1"
      image:
        repository: "dagster/k8s-example"
        tag: latest
        pullPolicy: Always
      dagsterApiGrpcArgs:
        - "-f"
        - "/example_project/example_repo/repo.py"
      port: 3030
  deployments:
    - name: "k8s-example-user-code-2"
      image:
        repository: "dagster/k8s-example"
        tag: latest
        pullPolicy: Always
      dagsterApiGrpcArgs:
        - "-f"
        - "/example_project/example_repo/repo.py"
      port: 3030
j
Just a small syntax error, there should just be a single ‘deployments’ field with 2 list items
Copy code
userDeployments:
  enabled: true
  deployments:
    - name: "k8s-example-user-code-1"
      image:
        repository: "dagster/k8s-example"
        tag: latest
        pullPolicy: Always
      dagsterApiGrpcArgs:
        - "-f"
        - "/example_project/example_repo/repo.py"
      port: 3030
    - name: "k8s-example-user-code-2"
      image:
        repository: "dagster/k8s-example"
        tag: latest
        pullPolicy: Always
      dagsterApiGrpcArgs:
        - "-f"
        - "/example_project/example_repo/repo.py"
      port: 3030
It would be nice if helm could warn on the duplicate key error
j
Great, thanks a lot - both are showing up now
👍 1