Merge pull request #3055 from manics/self-hosted-k8s

Replace microk8s with generic self-hosted doc

Author: consideRatio

docs/source/conf.py

@@ -215,6 +215,7 @@ def parse_schema(d, md=[], depth=0, pre=""):
     "microsoft/step-zero-azure-autoscale": "kubernetes/microsoft/step-zero-azure",
     "microsoft/step-zero-azure": "kubernetes/microsoft/step-zero-azure",
     "google/step-zero-gcp": "kubernetes/google/step-zero-gcp",
+    "kubernetes/other-infrastructure/step-zero-microk8s": "kubernetes/other-infrastructure/step-zero-other",
     "create-k8s-cluster": "kubernetes/setup-kubernetes",
     "turn-off": "jupyterhub/uninstall",
     "setup-jupyterhub": "jupyterhub/index",

docs/source/kubernetes/other-infrastructure/.gitkeep

@@ -0,0 +1,23 @@
+(self-hosted-k8s)
+
+# Self-hosted Kubernetes
+
+The Zero to JupyterHub guide assumes you're using a managed Kubernetes service with one of the main cloud platforms.
+
+JupyterHub can be deployed on a self-hosted Kubernetes cluster, but this is not officially supported.
+However you may be able to get help, and find examples of other self-hosted deployments, on the [Jupyter community forum](https://discourse.jupyter.org/c/jupyterhub/10).
+
+## Kubernetes cluster requirements
+
+Z2JH assumes your Kubernetes cluster has the following features:
+
+- [Dynamic Volume Provisioning](https://kubernetes.io/docs/concepts/storage/dynamic-provisioning/) for persistent storage
+- [LoadBalancer](https://kubernetes.io/docs/concepts/services-networking/service/#loadbalancer) or [Ingress](https://kubernetes.io/docs/concepts/services-networking/ingress/) for managing external access to JupyterHub
+
+Z2JH assumes you have full administrator access to the cluster.
+
+In many cases you need to consult your Kubernetes provider's documentation to find out how to enable these features.
+Please test all these features with a simple deployment before proceeding with the Zero to JupyterHub guide.
+Z2JH has several interacting components which makes it much more difficult to debug Kubernetes problems, so you will save a lot of time by verifying your cluster is working correctly first.
+
+It is possible to deploy Z2JH without some features, for example by [disabling persistent storage](schema_singleuser.storage.type) or using [NodePort](schema_proxy.service.type), but this is only suitable for testing.

docs/source/kubernetes/other-infrastructure/step-zero-microk8s.md

@@ -19,7 +19,7 @@ redhat/step-zero-openshift
 ibm/step-zero-ibm
 digital-ocean/step-zero-digital-ocean
 ovh/step-zero-ovh
-other-infrastructure/step-zero-microk8s
+other-infrastructure/step-zero-other
 ```
 
 ```{note}