We should do the following on CI:
It looks from https://github.com/jupyterhub/zero-to-jupyterhub-k8s/blob/master/ci/test.sh that we're now testing that pods are up and running...so I'm gonna close this, but please re-open if I'm missing something and there's still something to be done!
ci/test.sh only checks JupyterHub is running, it doesn't check singleuser servers can be started. That's arguably covered by https://github.com/jupyterhub/zero-to-jupyterhub-k8s/issues/639 though.
ah nice catch @manics ! I'm re-opening this, and we should cross-close it when a fix for #639 comes in
What is the status of this issue? We'd like to start running CI for our deployment and its not clear how to implement this.
As mentioned on https://github.com/jupyterhub/zero-to-jupyterhub-k8s/issues/639#issuecomment-380049228 I haven't had time to look at automatically testing servers after deployment.
@manics made a god suggestion in https://github.com/jupyterhub/mybinder.org-deploy/pull/663: adding more extensive tests on a real k8s cluster.
I think more extensive testing with a "real" k8s setup is a great idea! Donating or providing the resources for doing this would be an easy way for some of the many users of the z2jh guide to help out with making the guide better and more stable.
Working towards this in #846.
Done with @consideRatio help in https://github.com/jupyterhub/zero-to-jupyterhub-k8s/pull/1053 !
This is really excellent @manics !!! @minrk helped me out behind the scenes, especially regarding the cherry picked commits. I'm really happy you brought this all the way to the finish line @manics !
We may not have solved the "various configs" parts of this issue, right? I'm closing this for now and opening a new about "various configs" as I find this to be relevant as well.