# Error: no kind "Job" is registered for version "batch/v1" in scheme "k8s.io/kubernetes/pkg/api/legacyscheme/scheme.go:30"

**URL:** <https://discourse.jupyter.org/t/error-no-kind-job-is-registered-for-version-batch-v1-in-scheme-k8s-io-kubernetes-pkg-api-legacyscheme-scheme-go-30/2624>\
**Category:** Zero to JupyterHub on Kubernetes\
**Created:** [November 6, 2019, 11:34pm UTC](https://discourse.jupyter.org/t/error-no-kind-job-is-registered-for-version-batch-v1-in-scheme-k8s-io-kubernetes-pkg-api-legacyscheme-scheme-go-30/2624 "2019-11-06T23:34:58Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![arokem](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.jupyter.org/arokem/32/9_2.png) [@arokem](https://discourse.jupyter.org/u/arokem)\
**Post date:** [November 6, 2019, 11:34pm UTC](https://discourse.jupyter.org/t/error-no-kind-job-is-registered-for-version-batch-v1-in-scheme-k8s-io-kubernetes-pkg-api-legacyscheme-scheme-go-30/2624/1 "2019-11-06T23:34:58Z")

</div>

Hello! I have been following the z2jh documentation to deploy a JHub on AWS.

I got as far as launching a kubernetes cluster (following [these](https://zero-to-jupyterhub.readthedocs.io/en/latest/amazon/step-zero-aws.html) instructions) and proceeded to install and initialize helm. So far, so good.

When I try to run this step:

```auto
ubuntu@ip-172-31-32-95:~/config/jhub-config$ helm upgrade --install $RELEASE jupyterhub/jupyterhub --namespace $NAMESPACE --version=0.8.2 --values config.yaml

```

I get:

```auto
Release "jhub" does not exist. Installing it now.
Error: no kind "Job" is registered for version "batch/v1" in scheme "k8s.io/kubernetes/pkg/api/legacyscheme/scheme.go:30"

```

Does anyone know what this error means? My google-fu is failing me.

```auto

```

---

<div class="post-metadata">

**Author:** ![arokem](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.jupyter.org/arokem/32/9_2.png) [@arokem](https://discourse.jupyter.org/u/arokem)\
**Post date:** [November 7, 2019, 8:54pm UTC](https://discourse.jupyter.org/t/error-no-kind-job-is-registered-for-version-batch-v1-in-scheme-k8s-io-kubernetes-pkg-api-legacyscheme-scheme-go-30/2624/2 "2019-11-07T20:54:25Z")

</div>

Given the presence of `batch/v1`, and “Job”, I am guessing that maybe it’s related to [this template](https://github.com/jupyterhub/zero-to-jupyterhub-k8s/blob/ddf52e6522a2d9722a05121d86557becbdf7e742/jupyterhub/templates/image-puller/job.yaml). Could it be that the API version needs to be updated? In [other remotely similar cases](https://github.com/kubernetes/kubernetes/issues/55894) that seems to help.

---

<div class="post-metadata">

**Author:** ![arokem](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.jupyter.org/arokem/32/9_2.png) [@arokem](https://discourse.jupyter.org/u/arokem)\
**Post date:** [November 7, 2019, 9:47pm UTC](https://discourse.jupyter.org/t/error-no-kind-job-is-registered-for-version-batch-v1-in-scheme-k8s-io-kubernetes-pkg-api-legacyscheme-scheme-go-30/2624/3 "2019-11-07T21:47:51Z")

</div>

Some more info is that the kubectl versions on client and server are not within one minor version from each other:

```auto
kubectl version
Client Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.2", GitCommit:"c97fe5036ef3df2967d086711e6c0c405941e14b", GitTreeState:"clean", BuildDate:"2019-10-15T19:18:23Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.6", GitCommit:"96fac5cd13a5dc064f7d9f4f23030a6aeface6cc", GitTreeState:"clean", BuildDate:"2019-08-19T11:05:16Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"}

```

This may be a red herring too. I am still trying to figure out how to harmonize that, so if anyone knows, feel free to chime in. Otherwise, I will tell you when I figure it out.

---

<div class="post-metadata">

**Author:** ![betatim](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.jupyter.org/betatim/32/10_2.png) [@betatim](https://discourse.jupyter.org/u/betatim)\
**Post date:** [November 8, 2019, 6:08am UTC](https://discourse.jupyter.org/t/error-no-kind-job-is-registered-for-version-batch-v1-in-scheme-k8s-io-kubernetes-pkg-api-legacyscheme-scheme-go-30/2624/4 "2019-11-08T06:08:57Z")

</div>

I think the version difference shouldn’t matter. To update your local/client version you need to install a newer version of kubectl (in the same way you installed the original but with a new version).

Maybe you can disable the pre-puller in the config and deploy again to see what happens. WIth the pre-puller disabled this Job won’t be deployed so we should see the error go away.

---

<div class="post-metadata">

**Author:** ![arokem](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.jupyter.org/arokem/32/9_2.png) [@arokem](https://discourse.jupyter.org/u/arokem)\
**Post date:** [November 8, 2019, 11:10am UTC](https://discourse.jupyter.org/t/error-no-kind-job-is-registered-for-version-batch-v1-in-scheme-k8s-io-kubernetes-pkg-api-legacyscheme-scheme-go-30/2624/5 "2019-11-08T11:10:14Z")

</div>

Thanks @betatim! How do I disable the pre-puller in the config? To be clear, at the point at which I am issuing this `helm upgrade` my config file includes only the `proxy`/`secretToken` field.

---

<div class="post-metadata">

**Author:** ![arokem](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.jupyter.org/arokem/32/9_2.png) [@arokem](https://discourse.jupyter.org/u/arokem)\
**Post date:** [November 8, 2019, 11:15am UTC](https://discourse.jupyter.org/t/error-no-kind-job-is-registered-for-version-batch-v1-in-scheme-k8s-io-kubernetes-pkg-api-legacyscheme-scheme-go-30/2624/6 "2019-11-08T11:15:18Z")

</div>

OK: I think I found it, [here](https://zero-to-jupyterhub.readthedocs.io/en/latest/reference.html#prepuller)

---

<div class="post-metadata">

**Author:** ![arokem](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.jupyter.org/arokem/32/9_2.png) [@arokem](https://discourse.jupyter.org/u/arokem)\
**Post date:** [November 8, 2019, 11:19am UTC](https://discourse.jupyter.org/t/error-no-kind-job-is-registered-for-version-batch-v1-in-scheme-k8s-io-kubernetes-pkg-api-legacyscheme-scheme-go-30/2624/7 "2019-11-08T11:19:26Z")

</div>

I can confirm that following [these instruction](https://zero-to-jupyterhub.readthedocs.io/en/latest/optimization.html#pulling-images-before-users-arrive) indeed made my error go away. I’ll report back here if I run into any issues downstream from this.