Impossible to deploy in a specific namespace about zero-to-jupyterhub-k8s HOT 5 CLOSED

Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗

If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.

You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! 👋

Welcome to the Jupyter community! 🎉

from zero-to-jupyterhub-k8s.

Use the flag --namespace=my-namespace and it will work!

A chart installation is called release, and the .Release.Namespace value is populated based on where the helm command installing the chart is instructed to install it, so .Release.Namespace is not controlled as other .Values via chart configuration files.

It could make sense to assume we would see metadata.namespace set in the templates, but that field specifically is populated by helm without it being declared in the temolate.

from zero-to-jupyterhub-k8s.

More details at https://z2jh.jupyter.org btw!)

from zero-to-jupyterhub-k8s.

Thank you very much for your quick reply.

I tried the command below and the output does not have the namespace field.

helm install --dry-run --debug <REDACTED> --namespace=<REDACTED> --generate-name

Maybe I'm doing something wrong, but I appreciate any help.

from zero-to-jupyterhub-k8s.

Ah, I figure the interaction then is like kubectl apply --namespace my-namespace -f <some resource without metadata.namespace specified> which would then end up in the right namespace, but the generated resource didn't declare the namespace.

from zero-to-jupyterhub-k8s.