Advanced guide

• Creating image and push it to gcr.io
  • Create a docker file as in the directory user-image
  • Modify the Google project name in Makefile
  • Add some images and packages in Dockerfile if needed
  • Create docker file by: make
  • Check docker file present in your local pc or google cloud shell by: docker images
  • Push docker file to gcr.io: gcloud docker — push image_name
• Authentication

auth:
  type: github
  github:
    clientId: "4c4b0149fbee3d1eqw"
    clientSecret: "be560598fa89096f2e02f1ee72442d9b0eb277d5"
    callbackUrl: "http://notebooks.h-brs.de/hub/login"

• Automatic https

proxy:
  secretToken: ""
    https:
      hosts:
	- notebooks.mydomain.org
      letsencrypt:
	contactEmail: myemail@gmail.com

• If https does not work, eg. the port is not open, try specifying the loadBalancer IP
• nbgitpuller

singleuser:
  lifecycleHooks:
    postStart:
      exec:
	command: ["gitpuller", "https://github.com/username/my-repo", "master", "my-repo"]

• Modifying load balancer
  • Tweaking load balancer ip is useful when https port may not be open, and if it is the case create new ip and attach that ip to the load balancer.
  • You can change the load balancer ip by removing the old one and create new static ip and attach that new ip to the load balancer
  • Tell config.yaml this new ip

proxy:
  secretToken: ""
  service:
    type: LoadBalancer
    loadBalancerIP: a.b.c.d

• Configure node pools for core and user. This config has been used in the Binder configuration.
  • a "core" pool, which runs the hub, etc.
  • a "user" pool, where user pods run.
  • example: "hub.jupyter.org/node-purpose": "core" and "user"
  • More issue can be found here
• Let's encrypt automatic https update
  • Restart autohttps pod since the automatic https does not work with the current image of kube-lego we are using. For more information see the following issue
    • https://github.com/jupyterhub/zero-to-jupyterhub-k8s/issues/1033 (restart autohttps pod)
    • https://github.com/jupyterhub/zero-to-jupyterhub-k8s/issues/963
  • Manual restart (the pod name may be different autohttps-.....)

    * kubectl exec autohttps-6cc94589d-8fdxj -c kube-lego reboot -n prod
    * kubectl exec autohttps-6cc94589d-8fdxj -c nginx reboot -n prod