chauncy
chauncy
also, you will need to logout and log back in to trigger creation of the Team Space. you can force this by visiting the `/orbit/logout` URL
that's exactly what you should see. from there you can click on "Notebook Servers" on the left to launch or connect to previously launched notebooks.
we've not encountered a 503 on the status check before.. we have seen with complex network setups cause timeouts, but not a 503 returned by the jupyter server. did the...
it appears as though you created another User (tieho-boqo) through the kubeflow onboarding mechanism. this User is not a member of a TeamSpace and is not managed by Orbit. you...
you're still creating Notebooks in the wrong namespace (tieho-boqo). after logging in, before clicking on the Notebook Servers link, try clicking the drop down box in the upper left in...
creating namespaces with the kubeflow Namespace UI is not supported, these namespaces will not function. team namespaces are created when `orbit deploy teams` is run. user namespaces are created when...
were you able to resolve the missing teams/groups?
when you deleted the orbit-system namespace you removed the webhook declaration and pods. the image-replicator webhook updates Pod images to point to ECR and initiates a replication of public images...
this is usually a networking issue between EFS and the Nodes or Pods in the cluster. did you deploy EFS with the `orbit deploy foundation` or did you deploy your...
we have yet to find a way to customize the UI to represent the actual deployed Pod