https://datahubproject.io logo
Join Slack
Powered by
When I try to port forward my frontend pod and log...
# troubleshoot
r
When I try to port forward my frontend pod and log in with default username/pw, I get these errors from the frontend pod, It seems like the GMS pod could not be resolved but GMS pod gives out no error and is running fine. Anyone has any pointers?
Untitled.txt
e
Hey @rapid-house-76230 how are you running DataHub? Is this through the Docker quickstart?
r
hey Aditya, I’m deploying the components (GMS, Frontend) via k8s with Kustomize using the docker image 
:cfcc1cf
and have them talked to AWS OpenSearch (ElasticSearch) and a AWS Postgres db
e
Got it, does the frontend pod work okay if you don’t port forward?
It’s just giving this error when you port forward?
r
Yes, no errors or anything if I don’t tried to port forward and test it
This would only happen if I port forward, and try to log in
Here’s my GMS deployment yaml
Copy code
apiVersion: apps/v1
kind: Deployment
metadata:
  name: datahub-gms-deployment
  labels:
    app: datahub-gms
spec:
  replicas: 1
  selector:
    matchLabels:
      app: datahub-gms
  template:
    metadata:
      labels:
        app: datahub-gms
    spec:
      containers:
        - name: datahub-gms
          image: linkedin/datahub-gms:cfcc1cf
          ports:
            - containerPort: 8080
          env:
            - name: JAVA_OPTS
             ...
e
what steps are you taking to port forward?
r
(to clarify, I only port forward the frontend pod, not the GMS pod)
@echoing-airport-49548 do you think the issue is in my GMS config?
e
Let me dig into this for you and see if I can find out what might be going on
o
To clarify, you are able to access the frontend pod (through an ingress, open connection into the cluster, or through being on a machine within the cluster) and have no issues logging into DataHub without port-forwarding, but as soon as you port-forward you are no longer able to login? Or is it possible that GMS & the frontend pod are just not communicating? (which would not result in any immediate errors, the frontend would just not be able to pull data) Port-forwarding itself should not cause issues unless you're reusing one of the reserved ports.
r
Thanks @orange-night-91387 I think GMS and Frontend might not be communicating based on the errors that I get from frontend pod. The error happens as soon as I hit Sign In to datahub.
f
Hey @rapid-house-76230, can you show me your ingress config of the frontend?
r
This issue was resolved by updating my 
DATAHUB_GMS_HOST
to 
datahub-gms-service
instead of 
datahub-gms
(due to my k8s yaml config). Thanks @incalculable-ocean-74010!
2 Views
Open in Slack
PreviousNext
Powered by