The Epinio CLI will typically run on a host, which will need network access to your kubernetes cluster. Usually you will use the same host to run tooling, like e.g. "kubectl" and "helm".
The compiled binary will use about 40-50MB disk space, incl. local configuration files.
Epinio is a Kubernetes application and thus needs a running Kubernetes cluster for installation.
See system requirements about the Kubernetes environment Epinio expects to run on.
Refer to Install the Epinio CLI.
Beside advanced installation options, there are two ways of installing Epinio:
- For test environments. This should work on nearly any kubernetes distribution. Epinio will try to automatically create a magic DNS domain, e.g. 10.0.0.1.omg.howdoi.website.
- For test and production environments. You will have to define a system domain, e.g. test.example.com.
- Install on K3d - Install K3d and then install Epinio
- Install on Minikube - Install Minikube and then install Epinio
- Install on K3s - Install Epinio in k3s clusters
- Install on EKS - Install Epinio in Amazon EKS clusters
- Install on AKS - Install Epinio in Azure AKS clusters
- Install on GKE - Install Epinio in Google GKE clusters
- Install on RKE2 - Install Epinio in Rancher RKE2 clusters