This message was deleted.
# epinio
a
This message was deleted.
b
hey @full-accountant-59700, thanks for your honest feedback! That’s very important for us. Let me try to answer or ask you something more to get a deeper understanding, and see where we can improve. The no-experience with Kubernetes is meant to be from the developer point of you. Epinio is meant to be installed and configured on a Kubernetes cluster, so you need some experience for this step. But then, if you are a developer that is just using Epinio as a PaaS then you don’t need any experience, and you can use just the Epinio CLI to deploy and play with it. Regarding the installation part the youtube videos are probably very outdated. Right now you can install Epinio with just an Helm command, and the only requirement is to have
cert-manager
. So if you have a local k8s cluster (I usually use
k3d
) it’s just a matter of a
helm install epinio epinio/epinio
. The easiest way to do that is going through the quickstart. Did you eventually end up following other more complex installation scenarios? Let us know where we can improve!
❤️ 1
f
@broad-dream-81849 I tried in Linux Mint, in Ubuntu, in Debian, in OpenSuse, in Fedora (this distro was the first i tried, but the conda got bugged my terminal that i needed to reinstall my whole machine). Now, lesson learned. I am trying to install in a Ubuntu machine with VirtualBox and let's see what ahead. Let you know the other scenarios in a couple hours. Just to let you know, i'm not stopping until i see epinio running the easiest way possible. My idea after those frustrations is to set an shell script for Ubuntu deploy, with all dependencies, cert-manager and k3d, installing afterwards the epinio solution in one single instance. I'm not satisfied. Easiest is easiest. Not kinda easy. 🙂 We talk shortly. Thanks for the fast reply do. 😉
b
for a local development k3d is very easy. It’s kubernetes (k3s) in docker, so once you have your favorite distro running with docker installed you are good to go. And you will be pretty confident to not mess up your machine! Anyway, if you find any issue just let me know. 🙂
🙌 1
also one more thing to be aware while running Epinio locally is that you will need to use something like sslip.io to use a proper domain that will resolve to your local address 👍
👀 1
b
yeah, use k3d... anyway, given u that script... u should be on your way to test developer's experience point of view. You need to have some k8 knowledge in order to install this, this is true... I am from developer to doing k8 and it is not fun! and this is why you need epinio.
f
I am in the sslip.io part.
I am getting always the ´Error: Kubernetes cluster unreachable: Get "http://localhost:8080/version": dial tcp 127.0.0.18080 connect: connection refused´
Omg.. I installed epinio but i dont know what i did... After helm stopped giving ´connection refused´ errors, i installed the sslip docker image, i tried once more install the cert-manager... after the cert-manager got installed, i finally got installed epinio... But without any huge commands to follow. @busy-teacher-96897, i didnt got the chance to use your https://gist.github.com/gitricko/b5125a3649e5d52faec4e4f9a496e166 Makefile... This file was only helpful to ´check-dependencies:´ and give the ´epinio - ok´ part...
b
Welcome to the world of k8. You should still try the makefile :-)
👀 1
“I don’t know what I did” is very normal in k8
🎯 1
f
Nicelly putted. 🤣🤣🤣
But tomorrow, i am going, still, re-install all over again and see step by step how i arrived successfully in epinio installation without the bumps that i have.
Thanks soo much for now.. @busy-teacher-96897 @broad-dream-81849. Going to push the updates in my github.
b
That script is one of them but using k3d as the k8. But yes, you need to have a script that automates from zero
f
I was remembering here, i was able to install thanks to this Makefile. I thought not, but it worked. As in mention, “I don’t how i did”.. hehe
😉 1