https://dagster.io/ logo
a

Adrian

01/07/2021, 10:03 PM
hi guys - I'm setting up Dagster using the helm_chart (using Terraforms helm_release provider) in the values.yml. I enabled ingress for Dagit and it generated the following the ingress in posted below in the thread. I've setup Nginx as the load balancer but it doesn't seem to be picking it up. What could I be missing?
Ingress generated by the chart...
Copy code
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  annotations:
    <http://meta.helm.sh/release-name|meta.helm.sh/release-name>: dagster
    <http://meta.helm.sh/release-namespace|meta.helm.sh/release-namespace>: dagster
  creationTimestamp: "2021-01-07T21:31:11Z"
  generation: 1
  labels:
    <http://app.kubernetes.io/instance|app.kubernetes.io/instance>: dagster
    <http://app.kubernetes.io/managed-by|app.kubernetes.io/managed-by>: Helm
    <http://app.kubernetes.io/name|app.kubernetes.io/name>: dagster
    <http://app.kubernetes.io/version|app.kubernetes.io/version>: 0.9.22
    <http://helm.sh/chart|helm.sh/chart>: dagster-0.9.22
  managedFields:
  - apiVersion: extensions/v1beta1
    fieldsType: FieldsV1
    fieldsV1:
      f:metadata:
        f:annotations:
          .: {}
          f:<http://meta.helm.sh/release-name|meta.helm.sh/release-name>: {}
          f:<http://meta.helm.sh/release-namespace|meta.helm.sh/release-namespace>: {}
        f:labels:
          .: {}
          f:<http://app.kubernetes.io/instance|app.kubernetes.io/instance>: {}
          f:<http://app.kubernetes.io/managed-by|app.kubernetes.io/managed-by>: {}
          f:<http://app.kubernetes.io/name|app.kubernetes.io/name>: {}
          f:<http://app.kubernetes.io/version|app.kubernetes.io/version>: {}
          f:<http://helm.sh/chart|helm.sh/chart>: {}
      f:spec:
        f:rules: {}
    manager: Go-http-client
    operation: Update
    time: "2021-01-07T21:31:11Z"
  name: dagster-ingress
  namespace: dagster
  resourceVersion: "220746"
  selfLink: /apis/extensions/v1beta1/namespaces/dagster/ingresses/dagster-ingress
  uid: ace3c8a9-5930-478e-8764-d11eb392dadd
spec:
  rules:
  - http:
      paths:
      - backend:
          serviceName: dagster-dagit
          servicePort: 80
        path: /*
        pathType: ImplementationSpecific
status:
  loadBalancer: {}
The helm release...
Copy code
resource "helm_release" "dagster" {
  name       = "dagster"

  repository = "<https://dagster-io.github.io/helm>"
  chart      = "dagster"

  namespace = "dagster"

  # deploy to the dagster node pool
  set {
    name  = "affinity.nodeAffinity.requiredDuringSchedulingIgnoredDuringExecutionnodeSelectorTerms[0].matchExpressions[0].key[0]"
    value = "dagitnp"
  }
  set {
    name  = "affinity.nodeAffinity.requiredDuringSchedulingIgnoredDuringExecution.nodeSelectorTerms[0].matchExpressions[0].operator[1]"
    value = "In"
  }
  
  # allow gRPC triggers
  set {
    name = "userDeployments.enabled"
    value = true
  }

  set {
    name = "ingress.enabled"
    value = true
  }

}
r

rex

01/07/2021, 10:47 PM
Just to clarify, when you say nginx as the load balancer, you’re setting up an nginx ingress controller?
a

Adrian

01/07/2021, 11:46 PM
ah yes, ingress controller
r

rex

01/08/2021, 1:17 AM
I’m assuming you’re looking at https://docs.nginx.com/nginx-ingress-controller/installation/installation-with-helm/ for the nginx ingress controller
What kubernetes version are you using? Looks like in 1.18 there was a change that introduces an
IngressClass
which it looks like we don’t currently support on our ingress
controller.useIngressClassOnly
might be causing this to ignore the ingress setup by our helm chart
8 Views