# Chart missing jupyter- prefix?
**URL:** https://discourse.jupyter.org/t/chart-missing-jupyter-prefix/12684
**Category:** Zero to JupyterHub on Kubernetes
**Created:** [January 20, 2022, 11:16pm UTC](https://discourse.jupyter.org/t/chart-missing-jupyter-prefix/12684 "2022-01-20T23:16:59Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@brsolomon-deloitte](https://discourse.jupyter.org/u/brsolomon-deloitte)
#### Post date: [January 20, 2022, 11:16pm UTC](https://discourse.jupyter.org/t/chart-missing-jupyter-prefix/12684/1 "2022-01-20T23:16:59Z")
Despite the definition of `jupyterhub.fullname` in `_helpers-names.tpl`, a templating of `jupyterhub` 1.2.0 chart does _not_ seem to prefix resource names with `jupyter-`.
This seems odd; isn’t the point of `jupyterhub.fullname.dash` to default to `jupyter-` to avoid clashing names with other resources?
```bash
$ helm pull --untar --version 1.2.0 --repo https://jupyterhub.github.io/helm-chart/ jupyterhub
$ cd jupyterhub
$ helm template . | grep -A 10 'kind: Deployment'
kind: Deployment
metadata:
name: hub
labels:
component: hub
app: jupyterhub
release: RELEASE-NAME
chart: jupyterhub-1.2.0
heritage: Helm
spec:
replicas: 1
--
kind: Deployment
metadata:
name: proxy
labels:
component: proxy
app: jupyterhub
release: RELEASE-NAME
chart: jupyterhub-1.2.0
heritage: Helm
spec:
replicas: 1
--
kind: Deployment
metadata:
name: user-scheduler
labels:
component: user-scheduler
app: jupyterhub
release: RELEASE-NAME
chart: jupyterhub-1.2.0
heritage: Helm
spec:
replicas: 2
```
Notice in the above that all the resources (Deployments in this example) do _not_ have a `jupyter-` prefix on their `name`.
My Go templating know-how is not strong enough to fully understand [zero-to-jupyterhub-k8s/\_helpers-names.tpl at 4d5c9ca123927930d33a4a501f612e81bab5f7e9 · jupyterhub/zero-to-jupyterhub-k8s · GitHub](https://github.com/jupyterhub/zero-to-jupyterhub-k8s/blob/4d5c9ca123927930d33a4a501f612e81bab5f7e9/jupyterhub/templates/_helpers-names.tpl#L22) though, perhaps I am misinterpreting.
---
### Author:  [@brsolomon-deloitte](https://discourse.jupyter.org/u/brsolomon-deloitte)
#### Post date: [January 20, 2022, 11:24pm UTC](https://discourse.jupyter.org/t/chart-missing-jupyter-prefix/12684/2 "2022-01-20T23:24:25Z")
Debugging with a ConfigMap
```auto
kind: ConfigMap
apiVersion: v1
metadata:
name: findme
labels:
{{- include "jupyterhub.labels" . | nindent 4 }}
data:
jupyterhub.fullname: {{ include "jupyterhub.fullname" . }}
jupyterhub.fullname.dash: {{ include "jupyterhub.fullname.dash" . }}
jupyterhub.hub.fullname: {{ include "jupyterhub.hub.fullname" . }}
```
Result:
```bash
$ helm template . | grep -A 10 findme
name: findme
labels:
component: configmap-debug
app: jupyterhub
release: RELEASE-NAME
chart: jupyterhub-1.2.0
heritage: Helm
data:
jupyterhub.fullname:
jupyterhub.fullname.dash:
jupyterhub.hub.fullname: hub
```
Helm: v3.7.2
---
### Author:  [@minrk](https://discourse.jupyter.org/u/minrk)
#### Post date: [January 21, 2022, 11:38am UTC](https://discourse.jupyter.org/t/chart-missing-jupyter-prefix/12684/3 "2022-01-21T11:38:32Z")
The `jupyter-` prefix is only applied to user pods, not JupyterHub components, which are the hub, the proxy, etc.
You can set `fullnameOverride` in your config to define the prefix for jupyterhub components. It is an empty string by default, mostly for backward-compatibility reasons. There’s more info [in the docs](https://z2jh.jupyter.org/en/latest/resources/reference.html#fullnameOverride). The two main values to use are `null` to derive the value from the release and chart name, or an explicit string.
```auto
helm template --set fullnameOverride=null jupyterhub/jupyterhub --version=1.2.0 | grep -A 2 Deployment
```
gives
```auto
kind: Deployment
metadata:
name: RELEASE-NAME-jupyterhub-hub
--
kind: Deployment
metadata:
name: RELEASE-NAME-jupyterhub-proxy
--
kind: Deployment
metadata:
name: RELEASE-NAME-jupyterhub-user-scheduler
```
or to set it to a specific value:
```auto
helm template --set fullnameOverride=prefix jupyterhub/jupyterhub --version=1.2.0 | grep -A 2 Deployment
```
for
```auto
kind: Deployment
metadata:
name: prefix-hub
--
kind: Deployment
metadata:
name: prefix-proxy
--
kind: Deployment
metadata:
name: prefix-user-scheduler
```
---
### Author:  [@brsolomon-deloitte](https://discourse.jupyter.org/u/brsolomon-deloitte)
#### Post date: [January 21, 2022, 1:08pm UTC](https://discourse.jupyter.org/t/chart-missing-jupyter-prefix/12684/4 "2022-01-21T13:08:29Z")
> [@minrk](#):
>
> It is an empty string by default, mostly for backward-compatibility reasons.
Backwards compat considerations aside, this goes against a Helm best practice to provide some prefix by default. This is what [all the Bitnami charts do](https://github.com/bitnami/charts), for instance. A resource that’s just named `proxy` is overly generic and has a high potential of conflicting with another app’s resource. Placing each single application in its own namespace is not a common enough approach to assume this is the base case.