hey guys, just trying to install datahub this week...
# all-things-deployment
m
hey guys, just trying to install datahub this week using the latest helm chart and fluxcd on eks and running into this error: (I am not manually trying to override that value in my own values.yaml.
Copy code
│   Warning  error   25m (x8 over 25m)  helm-controller  Helm install failed: template: datahub/charts/datahub-mce-consumer/templates/deployment.yaml:61:27: executing "datahub/charts/datahub-mce-consumer/templa │
│ tes/deployment.yaml" at <.Values.global.datahub.monitoring.enablePrometheus>: nil pointer evaluating interface {}.enablePrometheus
looks like this param was added in the latest release 6 days ago
b
@orange-night-91387 Are you able to help dean with this one? I don't believe we've seen this yet
i
Hey Dean, What version of the helm charts are you using? Could you share your values.yaml?
m
hey @incalculable-ocean-74010 sure thing: I am using the latest version of the helm charts published on the helm repo.
Copy code
values:
    # <https://github.com/acryldata/datahub-helm/blob/master/charts/datahub/values.yaml>
    datahub-ingestion-cron:
      enabled: true

    datahub-frontend:
      service: 
        type: "ClusterIP"

      # OIDC auth based on <https://datahubproject.io/docs/authentication/guides/sso/configure-oidc-react>
      oidcAuthentication:
        enabled: true
        provider: okta
        clientId: 
          valueFrom:
            secretKeyRef:
              name: datahub-okta-client-details
              key: okta-client-id
        clientSecret:
          valueFrom:
            secretKeyRef:
                name: datahub-okta-client-details
                key: okta-client-secret
        oktaDomain: "<obfuscated>.<http://okta.com|okta.com>"

    mysqlSetupJob:
      enabled: false

    postgresqlSetupJob:
      enabled: true

    global:
      graph_service_impl: neo4j
      datahub_analytics_enabled: false
      datahub_standalone_consumers_enabled: true

      neo4j:
        username: "neo4j"
        password:
          secretRef: datahub-neo4j-basic-auth-credentials
          secretKey: neo4j-password

      sql:
        datasource:
          host: "postgres-primary.datahub.svc:5432"
          hostForpostgresqlClient: "postgres-primary.datahub.svc"
          port: "5432"
          url: "jdbc:<postgresql://postgres-primary.datahub.svc:5432/datahub>"
          driver: "org.postgresql.Driver"
          database: postgres
          username: "postgres"
          password:
            secretRef: postgres-pguser-postgres
            secretKey: password

        encryptionKey:
          secretRef: "datahub-encryption-secrets"
          secretKey: "encryption_key_secret"
          # Set to false if you'd like to provide your own secret.
          provisionSecret: true

        metadata_service_authentication:
          enabled: false
          systemClientId: "__datahub_system"
          systemClientSecret:
            secretRef: "datahub-auth-secrets"
            secretKey: "token_service_signing_key"
          tokenService:
            signingKey:
              secretRef: "datahub-auth-secrets"
              secretKey: "token_service_signing_key"
            salt:
              secretRef: "datahub-auth-secrets"
              secretKey: "token_service_salt"
          # Set to false if you'd like to provide your own auth secrets
          provisionSecrets: true
i
What is the output of
helm search repo
Copy code
datahub/datahub                    	0.2.89       	0.8.43     	A Helm chart for LinkedIn DataHub
?
The issue is with
global.datahub_standalone_consumers_enabled: true
Can you please set this to false?
There is currently a known bug with running consumers in standalone mode
Oddly enough, I’m not able to reproduce this issue locally.
Do you have a
Chart.yaml
file? If yes can you share it?
m
i am currently off at the moment but will try your suggestion. oddly i actually had the whole thing working last week but i tore it down yesterday and was trying to deploy it again and was running into this problem (i think because it was pulling a newer release).
i
Helm will only pull the version you have set in your
chart.yaml
, if you haven’t changed that then helm should not be pulling a newer release. Now this error was something we had in prior version of the helm. I fixed it in the latest release, or so I thought.
m
so im not setting a version when pulling from helm, i will try that as well (i assumed it would just pull the latest one but maybe thats wrong)
i
I think it pulls whatever latest you have in your cache which only gets updated if you run
helm repo up
I would highly recommend you set the chart version.
For consistent deployments
m
Cheers will make sure I do that thanks