Open zonca opened 2 years ago
Or maybe is it possible to run it just internally to Kubernetes just for users of JupyterHub with no ingress?
Or maybe is it possible to run it just internally to Kubernetes just for users of JupyterHub with no ingress? That's a popular option, for sure.
Not sure what would be different about naming the ServiceX ingress https://servicex-supercdms.jetstream-cloud.org
- that is supported by the current chart, or is that the thing Jetstream admins don't want to support?
Or maybe is it possible to run it just internally to Kubernetes just for users of JupyterHub with no ingress? That's a popular option, for sure.
Not sure what would be different about naming the ServiceX ingress
https://servicex-supercdms.jetstream-cloud.org
- that is supported by the current chart, or is that the thing Jetstream admins don't want to support?
yes exactly, they don't support that
I'll keep using zonca.dev
for now, @BenGalewsky @pibion let me know if you think about another option
@BenGalewsky @pibion
I am trying to deploy ServiceX to Jetstream (https://github.com/pondd-project/pondd-jetstream/pull/1)
the kubernetes deployment there is located at https://supercdms.jetstream-cloud.org/ and serves Jupyterhub. For servicex I need another subdomain. I don't want to ask jetstream to provide me other domains, it is not a service they generally provide.
Is there another domain I can use? Easier would be a CNAME to supercdms.jetstream-cloud.org