Hi guys, is it possible to use other kubternets distributions instead of minikube or microk8s like k3s or k3d?

k3s and k3d should both work 🙌🏻

Great. Installation is done as described here using kubectl? https://docs.orchest.io/en/stable/getting_started/installation.html#installing-orchest-using-kubectl

I would follow the installation instruction (where applicable) of Cloud > GKE. Installing orchest using the

orchest-cli

is easier. Let me know whether that works for you. @Navid H is, afaik, currently working on adding installation instructions for k3s.

Thanks. If I do not get it installed, I´ll simply use minikube. Should be fine for testing it on my EC2 instance.

Sounds good! Keep us updated 🙏

This is running for nearly 1h now...🤔

@Volker Lorrmann: Did you enable ingress addon in minikube?

I don´t think so. I am an absolute K8s newbie. 🙂

unfortunately k3s is not supported yet, it will be soon. we advise you to use minikube or mikrok8s for testing.

Ok thanks. Thank!

@Jacopo: I remember you had experience using nginx on the node to proxy requests to minikube ip. Could you help out here?

You can use the following snippet:

sudo apt-get install -y nginx

# Make Orchest accessible on the instance through <http://localorchest.io|localorchest.io>
minikube ip | xargs printf "%s <http://localorchest.io|localorchest.io>" | sudo tee -a  /etc/hosts

# Set up a reverse proxy that listens on port 80 of the host
# and routes traffic to Orchest
sudo cat << EOF > /etc/nginx/sites-available/localorchest.io
map $http_upgrade $connection_upgrade {
    default upgrade;
    ''      close;
}

server {
	listen 80 default_server;
	listen [::]:80 default_server;

	server_name orchest;

	location / {
		proxy_pass <http://localorchest.io>;

		# For project or file manager uploads.
		client_max_body_size 0;

		# WebSocket support.
		proxy_http_version 1.1;
		proxy_set_header Upgrade $http_upgrade;
		proxy_set_header Connection $connection_upgrade;
		proxy_read_timeout 86400;
	}
}
EOF

sudo ln -s /etc/nginx/sites-available/localorchest.io /etc/nginx/sites-enabled/
# Remove default_server.
sudo truncate -s 0 /etc/nginx/sites-available/default
sudo service nginx restart

sure thing 💪🏼

Wow. Thanks! I think this can be used for any other (remote) VM. Right?

Pretty much yes! Good point. The documentation should not just mention EC2 as it should work on all (afaik) linux hosts.

At least for me, there was a "sudo" in front of "cat" needed.

Thanks. I've edited the message for future reference 💪

@Volker Lorrmann apologies for the incorrect information, looks like we had some details to figure out for k3s to work. It should be supported soon. @Navid H will post here once the necessary changes are live