Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 26 additions & 0 deletions content/downloads/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,6 +25,32 @@ Starting with SPIRE v0.10.0, a `spire-extras` tarball is available that contains

{{< releases >}}

# Container Images

Official SPIRE container images are published to the GitHub Container Registry with each release:

* [`ghcr.io/spiffe/spire-server`](https://github.com/spiffe/spire/pkgs/container/spire-server)
* [`ghcr.io/spiffe/spire-agent`](https://github.com/spiffe/spire/pkgs/container/spire-agent)
* [`ghcr.io/spiffe/oidc-discovery-provider`](https://github.com/spiffe/spire/pkgs/container/oidc-discovery-provider)

Images are tagged with the release version number, without the leading `v`. For example, to pull the SPIRE Server and SPIRE Agent images for the latest release ({{< spire-latest "tag" >}}):

```bash
$ docker pull ghcr.io/spiffe/spire-server:{{< spire-latest "version" >}}
$ docker pull ghcr.io/spiffe/spire-agent:{{< spire-latest "version" >}}
```

# Helm Charts

For Kubernetes, the SPIRE stack is packaged as Helm charts by the [helm-charts-hardened](https://github.com/spiffe/helm-charts-hardened) project and published to the Helm repository at `https://spiffe.github.io/helm-charts-hardened/` (also browsable on [Artifact Hub](https://artifacthub.io/packages/helm/spiffe/spire)). This is the easiest and supported way to deploy a complete SPIRE stack in Kubernetes:

```bash
$ helm repo add spiffe https://spiffe.github.io/helm-charts-hardened/
$ helm repo update
```

See [About SPIRE Helm Charts Hardened](/docs/latest/spire-helm-charts-hardened-about/) for installation and configuration instructions.

@kfox1111 kfox1111 Jul 13, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
# System Packages
We have system packages available for some of the major distros.
## RPM based (Redhat / AlmaLinux / Rocky):
curl -o /etc/yum.repos.d/spire-examples.repo https://raw.githubusercontent.com/spiffe/spire-examples/refs/heads/main/examples/rpms/spire-examples.repo
## DEB based (Ubuntu / Debian)
### amd64
curl -o /etc/apt/sources.list.d/spire-examples.list https://raw.githubusercontent.com/spiffe/spire-examples/refs/heads/main/examples/debs/amd64/spire-examples.list
### arm64
curl -o /etc/apt/sources.list.d/spire-examples.list https://raw.githubusercontent.com/spiffe/spire-examples/refs/heads/main/examples/debs/arm64/spire-examples.list

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think if we want to advertise these we should have a good way of maintaining them. At the moment this seems to be done somewhat ad hoc and I'm not really sure why they are in spire-example. Would be good to start an issue about them, probably in SPIRE.

@kfox1111 kfox1111 Jul 13, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

They are maintained in spire-examples because they really belong in the various distro's. But, until that happens, we provide reference packages so people can onboard and use spire before the distro's are willing to support our users.

More details in: spiffe/club-zero#8

If your interested in helping maintain them, that would be great. :)

# Build from Source

To build SPIRE from source on Linux, you'll need:
Expand Down