```datahub-frontend: enabled: true image: ...
# troubleshoot
g
Copy code
datahub-frontend:
  enabled: true
  image:
    repository: linkedin/datahub-frontend-react
    tag: "v0.10.0"
  # Set up ingress to expose react front-end
  extraVolumes:
      - name: user-props
        secret:
          secretName: datahub-pass-secret
  extraVolumeMounts:
      - name: user-props
        mountPath: /datahub-frontend/conf/user.props
        subPath: token
        readOnly: true
  ingress:
    enabled: false
  resources:
    limits:
      memory: 1400Mi
    requests:
      cpu: 100m
      memory: 512Mi
Tried to upgrade the default password using this. Had created the secret before hand. Now my frontend is stuck in ContainerCreating. Any clue guys?
āœ… 1
b
are you trying to change the default password? the
subpath
should be
user.props
not
token
g
yes @better-orange-49102. Let me try again.
Copy code
datahub-frontend:
  enabled: true
  image:
    repository: linkedin/datahub-frontend-react
    tag: "v0.10.0"
  # Set up ingress to expose react front-end
  extraVolumes:
      - name: user-props
        secret:
          secretName: datahub-pass-secret
  extraVolumeMounts:
      - name: user-props
        mountPath: /datahub-frontend/conf/user.props
        subPath: user.props
        readOnly: true
  ingress:
    enabled: false
  resources:
    limits:
      memory: 1400Mi
    requests:
      cpu: 100m
      memory: 512Mi
Tried this @better-orange-49102. Still got a stuck containerCreating pod
Screenshot 2023-02-24 at 16.21.41.png
b
So run kubectl describe deploy datahub-datahub-frontend
g
Copy code
Development-Technology-Developer:~/environment $ kubectl describe deploy datahub-datahub-frontend
Name:                   datahub-datahub-frontend
Namespace:              default
CreationTimestamp:      Fri, 24 Feb 2023 00:01:02 +0000
Labels:                 <http://app.kubernetes.io/instance=datahub|app.kubernetes.io/instance=datahub>
                        <http://app.kubernetes.io/managed-by=Helm|app.kubernetes.io/managed-by=Helm>
                        <http://app.kubernetes.io/name=datahub-frontend|app.kubernetes.io/name=datahub-frontend>
                        <http://app.kubernetes.io/version=v0.10.0|app.kubernetes.io/version=v0.10.0>
                        <http://helm.sh/chart=datahub-frontend-0.2.136|helm.sh/chart=datahub-frontend-0.2.136>
Annotations:            <http://deployment.kubernetes.io/revision|deployment.kubernetes.io/revision>: 8
                        <http://meta.helm.sh/release-name|meta.helm.sh/release-name>: datahub
                        <http://meta.helm.sh/release-namespace|meta.helm.sh/release-namespace>: default
Selector:               <http://app.kubernetes.io/instance=datahub,app.kubernetes.io/name=datahub-frontend|app.kubernetes.io/instance=datahub,app.kubernetes.io/name=datahub-frontend>
Replicas:               1 desired | 1 updated | 1 total | 1 available | 0 unavailable
StrategyType:           RollingUpdate
MinReadySeconds:        0
RollingUpdateStrategy:  25% max unavailable, 25% max surge
Pod Template:
  Labels:           <http://app.kubernetes.io/instance=datahub|app.kubernetes.io/instance=datahub>
                    <http://app.kubernetes.io/name=datahub-frontend|app.kubernetes.io/name=datahub-frontend>
  Service Account:  datahub-datahub-frontend
  Containers:
   datahub-frontend:
    Image:       linkedin/datahub-frontend-react:v0.10.0
    Ports:       9002/TCP, 4318/TCP
    Host Ports:  0/TCP, 0/TCP
    Limits:
      memory:  1400Mi
    Requests:
      cpu:      100m
      memory:   512Mi
    Liveness:   http-get http://:http/admin delay=60s timeout=1s period=30s #success=1 #failure=4
    Readiness:  http-get http://:http/admin delay=60s timeout=1s period=30s #success=1 #failure=4
    Environment:
      ENABLE_PROMETHEUS:              true
      DATAHUB_GMS_HOST:               datahub-datahub-gms
      DATAHUB_GMS_PORT:               8080
      DATAHUB_SECRET:                 <set to the key 'datahub.gms.secret' in secret 'datahub-gms-secret'>  Optional: false
      DATAHUB_APP_VERSION:            1.0
      DATAHUB_PLAY_MEM_BUFFER_SIZE:   10MB
      DATAHUB_ANALYTICS_ENABLED:      true
      KAFKA_BOOTSTRAP_SERVER:         <http://b-2.mskdatahub.0c8aba.c9.kafka.us-east-1.amazonaws.com:9092,b-1.mskdatahub.0c8aba.c9.kafka.us-east-1.amazonaws.com:9092|b-2.mskdatahub.0c8aba.c9.kafka.us-east-1.amazonaws.com:9092,b-1.mskdatahub.0c8aba.c9.kafka.us-east-1.amazonaws.com:9092>
      ELASTIC_CLIENT_HOST:            <http://vpc-opensearch-domain-datahub-hi2fxo5vxkrylnmkcf563cdadu.us-east-1.es.amazonaws.com|vpc-opensearch-domain-datahub-hi2fxo5vxkrylnmkcf563cdadu.us-east-1.es.amazonaws.com>
      ELASTIC_CLIENT_PORT:            443
      ELASTIC_CLIENT_USE_SSL:         true
      ELASTIC_CLIENT_USERNAME:        opensearch
      ELASTIC_CLIENT_PASSWORD:        <set to the key 'elasticsearch-password' in secret 'elasticsearch-secrets'>  Optional: false
      DATAHUB_TRACKING_TOPIC:         DataHubUsageEvent_v1
      METADATA_SERVICE_AUTH_ENABLED:  true
      DATAHUB_SYSTEM_CLIENT_ID:       __datahub_system
      DATAHUB_SYSTEM_CLIENT_SECRET:   <set to the key 'token_service_signing_key' in secret 'datahub-auth-secrets'>  Optional: false
    Mounts:                           <none>
  Volumes:                            <none>
Conditions:
  Type           Status  Reason
  ----           ------  ------
  Available      True    MinimumReplicasAvailable
  Progressing    True    NewReplicaSetAvailable
OldReplicaSets:  <none>
NewReplicaSet:   datahub-datahub-frontend-c8bcdd744 (1/1 replicas created)
Events:
  Type    Reason             Age                From                   Message
  ----    ------             ----               ----                   -------
  Normal  ScalingReplicaSet  23m (x2 over 79m)  deployment-controller  Scaled up replica set datahub-datahub-frontend-7c89856fd to 1
  Normal  ScalingReplicaSet  14s (x2 over 64m)  deployment-controller  Scaled down replica set datahub-datahub-frontend-7c89856fd to 0
@better-orange-49102
Jut one thing. I am updating the charts/datahub/values.yaml. Is that the right way? Or do I need to create a separate values.yaml
b
I used the same values.yaml
g
Okay @better-orange-49102. Same values too right?
b
And I'm not sure why the container is not up - kubectl logs show anything?
g
no logs since the container is not up yet
b
@bulky-electrician-72362 @incalculable-ocean-74010
I'm out of ideas sorry 😐
b
@glamorous-elephant-17130 do you have enough resources?
nodes available for you pod?
please describe the pod that's not being created
under the envents section it usually tells what's the issue
i
What is the output of:
Copy code
kubectl -n <namespace where datahub is deployed> get events --sort-by='.lastTimestamp'
Is GMS pod on the same version?
g
Hey guys apologies. I had made a mistake while creating the secret's name. @incalculable-ocean-74010’s command help me figure it out. Super thankful!!!