Hi Team - our datahub installation is done and eve...
# all-things-deployment
r
Hi Team - our datahub installation is done and everything seem to be up and running. However, when we increased the replicaCount for datahub-frontend from 1 to 3, our okta authentication seem to not work and our users are unable to login. Can someone help with this? Here is the datahub-frontend helm config
Copy code
datahub-frontend:
        replicaCount: 1
        revisionHistoryLimit: 10
        image:
          repository: image
          tag:
          pullPolicy: IfNotPresent
        imagePullSecrets: []
        nameOverride: ""
        fullnameOverride: ""
        serviceAccount:
          create: true
          annotations: {}
          name:
        podAnnotations: {}
        podSecurityContext: {}
        securityContext: {}
        service:
          type: ClusterIP # ClusterIP or NodePort
          port: 8080
          targetPort: http
          containerPort: 8080
          protocol: TCP
          name: http
          annotations:
            <http://consul.hashicorp.com/service-sync|consul.hashicorp.com/service-sync>: "true"
            <http://consul.hashicorp.com/service-name|consul.hashicorp.com/service-name>: "datahub-datahub-frontend"
        serviceMonitor:
          create: false
        ingress:
          enabled: false
          extraLabels: {}
          annotations: {}
          hosts:
            - host: datahub_frontend_url
              paths: []
              redirectPaths: []
          tls: []
        oidcAuthentication:
          enabled: true
          provider: okta
          clientId: client_id
          clientSecret: client_secret
          oktaDomain: oktadomain
          scope: "openid profile email"
        extraLabels: {}
        extraPodLabels: {}
        extraEnvs:
        - name: SERVER_PORT
          value: "8080"
        extraVolumes: []
        extraVolumeMounts: []
        extraInitContainers: []
        extraSidecars: []
        lifecycle: {}
        resources:
          limits:
            cpu: 2
            memory: 8Gi
          requests:
             cpu: 2m
             memory: 8Gi
        nodeSelector: {}
        tolerations: []
        affinity: {}
        env:
          JMXPORT: 1099
        exporters:
          jmx:
            enabled: false
        livenessProbe:
          initialDelaySeconds: 60
          periodSeconds: 30
          failureThreshold: 4
        readinessProbe:
          initialDelaySeconds: 60
          periodSeconds: 30
          failureThreshold: 4
        datahub:
          play:
            mem:
              buffer:
                size: "10MB"
        global:
          datahub_analytics_enabled: true
          elasticsearch:
            host: "es_host"
            port: "80"
          kafka:
            bootstrap:
              server: "kafka_broker:kafka_port"
          datahub:
            version: head
            gms:
              port: "8080"
            monitoring:
              enablePrometheus: true
            appVersion: "1.0"
            metadata_service_authentication:
              enabled: false
              systemClientId: "__datahub_system"
@gentle-night-56466 do you have any insight into this issue ?
r
@green-football-43791 might be able to speak to this!
g
Hey Dheeraj, I’m not too sure about this one, let me check in with the team.
How has your deployment been going? It’s been a bit since we last caught up!
r
Hey @delightful-ram-75848 and @green-football-43791 - this issue is sorted with a small hack. While scaling up, we had to delete the old pods for some reason
We are deployed in staging and currently dogfooding is going on
g
sounds good- let us know what the feedback is!
r
Absolutely