Installation of the Epinio CLI
epinio cli can be used to interact with a cluster that has Epinio installed on it.
Application developers shouldn't need to access the cluster directly. Requests to
the Epinio API server are authenticated with Basic Auth. No direct access to the cluster
is required (e.g. through kubectl).
From Homebrew (Linux and Mac)
Epinio has its own formula available in the homebrew/core tap.
brew install epinio
Alternatively, if you want to get the latest Epinio CLI faster, there is a custom tap you can use:
brew tap epinio/tap
brew install epinio/tap/epinio
From the Binary Releases
Find the latest version at Releases.
curl -o epinio -L https://github.com/epinio/epinio/releases/download/v1.9.0/epinio-linux-x86_64
curl -o epinio -L https://github.com/epinio/epinio/releases/download/v1.9.0/epinio-darwin-x86_64
curl -LO https://github.com/epinio/epinio/releases/download/v1.9.0/epinio-windows-x86_64.zip
Extract the zip archive and put the binary in a directory that is in your
PATH environment variable. Instructions on how to add directories to the
PATH vary depending on your version of Windows.
Make the Binary Executable (Linux and Mac)
chmod +x epinio
Move the binary to your PATH
sudo mv ./epinio /usr/local/bin/epinio
Verify Downloaded Files
This is done using the
The following commands were tested using cosign version 2.1.1.
Verify File Checksum Signature
Instead of signing all release assets, Epinio signs a checksums file containing the different release assets checksums. You can download/copy the three files 'epinio_1.9.0_checksums.txt.pem', 'epinio_1.9.0_checksums.txt.sig', 'epinio_1.9.0_checksums.txt' from the latest release.
curl -LO https://github.com/epinio/epinio/releases/download/v1.9.0/epinio_1.9.0_checksums.txt.pem
curl -LO https://github.com/epinio/epinio/releases/download/v1.9.0/epinio_1.9.0_checksums.txt.sig
curl -LO https://github.com/epinio/epinio/releases/download/v1.9.0/epinio_1.9.0_checksums.txt
Once you have the three files locally, you can execute the following command
cosign verify-blob \
--certificate-identity-regexp "https://github.com/epinio/epinio" \
--certificate-oidc-issuer "https://token.actions.githubusercontent.com" \
--cert epinio_1.9.0_checksums.txt.pem \
--signature epinio_1.9.0_checksums.txt.sig \
A successful output looks like
Now you can verify the assets checksum integrity.
Verify File Checksum Integrity
Before verifying the file integrity, you should first verify the checksum file signature. Once you’ve download both the checksums and your binary, you can verify the integrity of your file by running:
sha256sum --ignore-missing -c epinio_1.9.0_checksums.txt
For this check to be effective it is necessary that the local
epinio binary has the proper name as
listed in the checksum file, i.e.
For windows the checksum is for the zip archive, not for the binary inside.
Verify the Installation
epinio version to test the successful installation.
> epinio version
Epinio Version: v1.9.0
Go Version: go1.20