How to run Open edX on a local Kubernetes cluster?

[regisb]

Tutor makes it possible to run Open edX on a remote Kubernetes cluster: https://docs.tutor.overhang.io/k8s.html
But in such a setup the Kubernetes cluster needs to expose public endpoints that the IDAs use to communicate between each other. As a consequence, when deploying to a local Kubernetes cluster running on the laptop, tutor k8s launch will fail.

We should:

• Provide instructions (or at least clear pointers) to run a local Kubernetes cluster, using either: Minikube, k3s, microk8s or any other lightweight Kubernetes distribution.
• Identify the steps that fail during a typical deployment of Open edX with Tutor to that Kubernetes cluster.
• Address those issues, either by making changes to Tutor or by adding instructions to the Tutor docs.

[Henrrypg]

Hello @regisb, i was testing with minikube for Olive and it appears to works fine. tutor k8s launch didn't fail. And doing minikube tunnel + adding CMS and LMS hostnames to /etc/hosts pointing to the ip taken from caddy external ip (Image with example from my test) i can see the sites.

I can take this task and add docs

[regisb]

That would be absolutely amazing! Looking forward to the PR.

I'm wondering if there is a way to avoid the manual changes to /etc/hosts, though?

[jmbowman]

2U SRE also uses primarily minikube, although it's more due to a lack of alternatives when the choice was originally made than the result of a detailed comparison. I heard one downvote for k3s for reasons not yet explained. Still waiting on input from a few people, I'll comment again if any useful insights come out of it.

[Henrrypg]

@jmbowman Sure, thank you, i'll explore others alternatives before doing anything, i was testing to avoid the current necessary change in /etc/hosts with Minikube but without a good result for now (@regisb). I'll comment here when i have more info.

[jmbowman]

Another vote came in for kind because it's "more robust with less memory footprint". A couple of comparisons that were fairly informative:

• https://www.blueshoe.io/blog/minikube-vs-k3d-vs-kind-vs-getdeck-beiboot/
• https://dev.to/iblancasa/kubernetes-alternatives-to-work-on-locally-4b9b

Generally what I'm seeing is "alternatives to minikube came up to address its limitations, and they've been stealing features from each other since". I think the current state is that minikube is still the most popular and is competitive in features, some of the alternatives are a little more efficient in resource usage.

[feoh]

Another vote for minikube IMO is its very rich driver support.

Knowing that I can spin tutor up using my ProxMox servers as VM hosts and get all that centrally managed goodness is a big win in my book :)

MicroK8s also runs in a number of environments but the support seems a bit more hit and miss.

[regisb]

Thanks for your input ya'll! It's very much appreciated. Please keep posting your opinions here :)

[jmbowman]

A visual of relative popularity over time of the options I've seen mentioned so far, courtesy of https://star-history.com/:

[Shubhamsingh1998]

Hi I have set up this much, my services are running on it, I have caddy serving as load-balancer , the issue is my http request is going to caddy but caddy behaves like it doses have path to redirect that traffic. When I put the IP it shows White Page and when I Put hostname its gives 502 Gateway error.

can Some help with this issue