Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Required JWT token is missing #1495

Closed
jasonsmithio opened this issue Sep 7, 2018 · 6 comments
Closed

Required JWT token is missing #1495

jasonsmithio opened this issue Sep 7, 2018 · 6 comments

Comments

@jasonsmithio
Copy link
Contributor

I followed the deploy procedures outlined here: https://www.kubeflow.org/docs/started/getting-started-gke/

anytime I try to access the system (after all pods and services have deployed) I get this error message.

Required JWT token is missing

Everything seems to be working so I am not sure what's causing the issue. Thoughts?

@samuelmi2
Copy link

I also get this error. I've replicated it on Kubeflow version 0.2.2 and 0.2.4.

@samuelmi2
Copy link

I see this in my logs, not sure if it shows anything useful though:

{
 insertId:  "16gq2opg1p91k7o"  
 labels: {…}  
 logName:  "projects/samuelmi-hlmsmn-gce-211415/logs/ingress-shim"  
 receiveTimestamp:  "2018-09-11T16:10:22.247221856Z"  
 resource: {…}  
 severity:  "ERROR"  
 textPayload:  "ingress-shim controller: Re-queuing item "kubeflow/envoy-ingress" due to error processing: issuer.certmanager.k8s.io "" not found"  
 timestamp:  "2018-09-11T16:10:16Z"  
}

@samuelmi2
Copy link

another log entry:

{
 insertId:  "vmzpnog1pthd0i"  
 labels: {
  compute.googleapis.com/resource_name:  "fluentd-gcp-v2.0.17-txjnz"   
  container.googleapis.com/namespace_name:  "kubeflow"   
  container.googleapis.com/pod_name:  "tf-hub-0"   
  container.googleapis.com/stream:  "stderr"   
 }
 logName:  "projects/samuelmi-hlmsmn-gce-211415/logs/tf-hub"  
 receiveTimestamp:  "2018-09-11T16:17:57.302445190Z"  
 resource: {
  labels: {
   cluster_name:  "tf-kubeflow"    
   container_name:  "tf-hub"    
   instance_id:  "4081713818277476247"    
   namespace_id:  "kubeflow"    
   pod_id:  "tf-hub-0"    
   project_id:  "samuelmi-hlmsmn-gce-211415"    
   zone:  "us-west1-b"    
  }
  type:  "container"   
 }
 severity:  "ERROR"  
 textPayload:  "[I 2018-09-11 16:17:53.645 JupyterHub proxy:299] Checking routes
"  
 timestamp:  "2018-09-11T16:17:53Z"  
}

@jlewi
Copy link
Contributor

jlewi commented Oct 11, 2018

How are you connecting to JupyterHub? You get the JWT by going through the ingress that has IAP enabled. You can't connect via kubectl port-forward because you won't have a JWT.

@jasonsmithio
Copy link
Contributor Author

I haven't tried it with 0.3 yet so let me go do that. When I did 0.2.5(?) I just followed the steps, no port-forward and saw the issue.

@jlewi
Copy link
Contributor

jlewi commented Oct 23, 2018

Closing this issue as stale. Please reopen if its still relevant.

@jlewi jlewi closed this as completed Oct 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants