![]() ![]() ![]() The hub pod needs a PVC to store runtime metadata (like names of people who log in) in a sqlite db. Warning FailedScheduling 81s (x5 over 5m25s) default-scheduler 0/1 nodes are available: 1 pod has unbound immediate PersistentVolumeClaims. $ microk8s kubectl describe pod hub-766b95d6f9-vw9v4 -n jhub That showed me that it was still waiting for its PersistentVolumeClaim to come up. The deployments came up, but after the hub pod was stuck in PENDING state for a long time, I decided to do a kubectl describe on it. $ RELEASE=jhub NAMESPACE=jhub microk8s helm3 upgrade -cleanup-on-fail -install $RELEASE jupyterhub/jupyterhub -namespace $NAMESPACE -version=0.9.0 -values values.yml The docs mention a -create-namespace option but since that didn't work for me, I had to create the namespace manually using kubectl: The second step is to install the chart on your Kubernetes cluster using helm. Successfully got an update from the "jupyterhub" chart repository Hang tight while we grab the latest from your chart repositories. "jupyterhub" has been added to your repositoriesĪnd update all the repos to get the latest chart versions. The first step is to add the repo for the official JupyterHub helm chart: You can just enable it!Īfter enabling helm, I followed the steps in the awesome Zero to JupyterHub docs to set up JupyterHub. Also, you don't need to install helm separately. It comes pre-packaged with kubectl which you can invoke with microk8s kubectl. Microk8s v1.19.0 from Canonical* installed Microk8s is very easy to install on Ubuntu (No wonder! Both tools come from Canonical): Today I gave it a try and found those words to be true! In this post, I'll list down the steps (for future me) to set up working JupyterHub and Airflow instances on microk8s. Nemo had mentioned that microk8s is a lot better than minikube, and has perfected the developer experience. Till now, I haven't bothered installing anything on it just because of these long wait times. After a minikube start, it has been taking a long time to come up for me (maybe because of my smol laptop), and it also throws some errors before it finally comes up. Some days ago I set up minikube to put together a small demo (or at least some screenshots) for a talk. You are receiving this because you were mentioned.Day 24 - JupyterHub and Airflow on microk8s 10 September 2020 Triage notifications on the go with GitHub Mobile for iOS Reply to this email directly, view it on GitHub It's super easy - justĬlick "Sugest a change on this page" bottom-right button and you will beĪble to create Pull Request directly from there. One (and give back for the free software you get). Airflow is created by > 1800Ĭontributors and adding such documenation might be the first step to become If you do make it works, I would really appreciate if you make a PRĪdding a chapter about debugging on OpenShift. I have deployed other apps in the same k8s cluster based on a python base image and pip list works fine inside the containerīeta Was this translation helpful? Give feedback.īTW. When I run the command pip -version returns ( pip 21.2.4 from /usr/local/lib/python3.7/site-packages/pip (python 3.7). When I list the contents of directory (/usr/local/lib/python3.7/site-packages) using ls command, I do see 2 packages installed (wheel, pip). ![]() Pip show about a specific package works fine ( ex. Pip list command outputs nothing, no error message. I am trying to get the list of installed packages from inside the container using pip list in preparation of adding additional packages. I have deployed Airflow official image v2.1.2 using helm chart community edition and is up and running no issues. I have posted details in slack channel - Apache Airflow Community - troubleshooting The issue that I am having is that pip list returns nothing, no error message. I am also planning to install pip packages using dockerfile ( approach 1). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |