# Releases
Pomerium is shipped in multiple formats and architectures to suit a variety of deployment patterns. There are two binaries:
pomerium
is the primary server component. It is a monolithic binary that can perform the function of any services mode.pomerium-cli
(optional) is a command-line client for working with Pomerium. Functions include generating service accounts, and acting as an authentication helper for tools like kubtctl.
# pomerium
- Supported Operating Systems:
linux
,darwin
- Supported Architectures:
amd64
,arm64
# Binaries
Official binaries can be found on our GitHub Releases (opens new window) page.
ARCH=[your arch]
OS=[your os]
VERSION=[desired version]
curl -L https://github.com/pomerium/pomerium/releases/download/${VERSION}/pomerium-${OS}-${ARCH}.tar.gz \
| tar -z -x
# Packages
- Supported formats:
rpm
,deb
- Requires
systemd
support
Official packages can be found on our GitHub Releases (opens new window) page.
# Docker Image
Pomerium utilizes a minimal (opens new window) docker container (opens new window). You can find Pomerium's images on dockerhub (opens new window). Pomerium can be pulled in several flavors and architectures.
:vX.Y.Z
: which will pull the a specific tagged release (opens new window).$ docker run pomerium/pomerium:v0.1.0 --version v0.1.0+53bfa4e
:latest
: which will pull the most recent tagged release (opens new window).$ docker pull pomerium/pomerium:latest && docker run pomerium/pomerium:latest --version v0.2.0+87e214b
:master
: which will pull an image in sync with git's master (opens new window) branch.docker pull pomerium/pomerium:latest
# Helm
Pomerium maintains a helm (opens new window) chart for easy Kubernetes deployment with best practices https://helm.pomerium.io/ (opens new window)
helm repo add pomerium https://helm.pomerium.io
helm install pomerium/pomerium
See the README (opens new window) for up to date install options.
# Source
TIP
Officially supported build platforms are limited by envoy proxy (opens new window). If you have an enoy binary for your platform in your path at start time, pomerium
should function correctly.
git clone git@github.com:pomerium/pomerium.git
cd pomerium
make
./bin/pomerium --version
# pomerium-cli
- Supported Operating Systems:
linux
,darwin
,windows
,freebsd
- Supported Architectures:
amd64
,arm64
,armv6
,armv7
# Binaries
Official binaries can be found on our GitHub Releases (opens new window) page.
ARCH=[your arch]
OS=[your os]
VERSION=[desired version]
curl -L https://github.com/pomerium/pomerium/releases/download/${VERSION}/pomerium-cli-${OS}-${ARCH}.tar.gz \
| tar -z -x
# Packages
- Supported formats:
rpm
,deb
Official packages can be found on our GitHub Releases (opens new window) page.
# Homebrew
brew tap pomerium/tap
brew install pomerium-cli
# Source
git clone git@github.com:pomerium/pomerium.git
cd pomerium
make build NAME=pomerium-cli
./bin/pomerium-cli --help
# Release cycle
The current release cycle is aligned on a monthly basis. Pre-1.0.0
we target a MINOR
release on or around the first day of each month. We try to hit the targets as closely as possible, while still delivering a quality release.
Pomerium uses Semantic Versioning (opens new window). In practice this means for a given version number vMAJOR.MINOR.PATCH (e.g. v0.1.0
):
- MAJOR indicates an incompatible API change,
- MINOR indicates a new functionality in a backwards-compatible manner, and
- PATCH indicates a backwards-compatible bug fixe.
As Pomerium is still pre-v1.0.0
, breaking changes between releases should be expected.
To see difference between releases, please refer to the changelog and upgrading documents.