Skip to main content

SPIRE (spire)

Issues SPIFFE identities to the platform workloads: SPIRE servers sign the SVIDs, a SPIRE agent on each host attests the node with its manager certificate and serves the workload API.

Generated from catalog/services/spire.yaml: do not edit by hand.

Summary​

Version1.15.5
Useinstall and configure, configure and connect
Layerfunctional (AI catalog)
CategoryIdentity and secrets
Installation methodsbinary
External connectionno
Sandbox onlyno

Licence​

SPDX identifierApache-2.0
Licence policycore licence (MIT or Apache-2.0)
Licence exception-
Platform componentspire

Packages and artifacts​

A package the project of the service publishes (its image, its binary archive, its Python or OS package) carries the licence of the service; a third-party package carries the licence written on its row, read from the official upstream metadata.

KindPackageVersionLicenceDetails
binary archivespire-1.15.5-linux-amd64-musl.tar.gz1.15.5Apache-2.0https://github.com/spiffe/spire/releases/download/v1.15.5/spire-1.15.5-linux-amd64-musl.tar.gz, x86_64, checksum sha256

Supported systems and architectures​

MethodOperating systemsArchitectures
binaryRHEL family (dnf), Debian family (apt), Arch Linux (pacman)x86_64 (architecture of the artifacts of the descriptor)

Certified host systems: RHEL 8/9/10, Rocky Linux 8/9/10, AlmaLinux 8/9/10, Oracle Linux 8/9, CentOS Stream 9/10, Ubuntu 22.04/24.04, Debian 12, Arch Linux (rolling). The host preflight accepts these systems (other releases of a known family give a warning, end of life releases are refused) and the x86_64 and aarch64 architectures.

Prerequisites​

Host​

  • a synchronized clock (blocking, time_sync).

Network and ports​

ComponentPort namePortOpened in the host firewall
spire-servergrpc8081/tcpyes
spire-serverbundle8443/tcpyes
spire-serverhealth8080/tcpno
spire-servermetrics9988/tcpyes
spire-agenthealth8089/tcpno
spire-agentmetrics9989/tcpyes

Services and connections needed​

Details and resolution: see Dependencies.

Installation methods and modes​

MethodDefaultWhat the method uses
binaryyesthe binary archives of the descriptor, unpacked under the service directory

Components​

ComponentKindInstallation methodsPorts
SPIRE server (spire-server)masterbinary8081/tcp, 8443/tcp, 8080/tcp, 9988/tcp
SPIRE agent (spire-agent)workerbinary8089/tcp, 9989/tcp

Single server (standalone) (default)​

One SPIRE server with a local SQLite datastore, agents on any host.

What the mode deploys:

ComponentPlacement
spire-servermin 1, max 1
spire-agentmin 0

High availability (ha)​

Three SPIRE servers sharing a PostgreSQL datastore.

What the mode deploys:

ComponentPlacement
spire-servermin 3, max 3
spire-agentmin 0

Install this service​

The install wizard of the Navin Manager plans, validates and runs the installation; you need the services:install permission on the cluster.

  1. Open the wizard. In Clusters, choose the row action Install services of the target cluster. The wizard opens on its first step, Service.

  2. Choose the service. On the Service step, select SPIRE. The card shows the licence Apache-2.0 and the dependencies the installation needs.

  3. Choose the hosts and the mode. On the Hosts step, tick the hosts, then choose the Mode: standalone (default), ha. Each mode deploys the components listed in Installation methods and modes. With several components, place each one on its hosts in Component placement (Suggest placement proposes a placement that respects the cardinalities).

  4. Bind the dependencies. On the Bindings step, choose for each dependency (datastore) Install with the platform or Use an existing connection; an optional dependency can stay on No binding.

  5. Configure. On the Configure step, review the parameters (see Configuration parameters); the required ones are trust_domain. Passwords left empty with a generated default are generated and sealed by the Manager.

  6. Review and install. On the Install step the Manager validates the plan and shows the installation order; when it says "The plan is valid. Ready to install.", choose Install. A highly available mode is installed only when its HA checks pass.

  7. Verify. The operation ends when the health checks of every instance pass (see Health checks); the service then shows as running in Services.

Connect an existing service​

Schemeshttps
Default port8081
Authenticationnone
Health checkhealth_url + /ready
Authentication methodFieldsDescription
none-The SPIRE server API is reached over mutual TLS with the SPIFFE identities it issues itself; the Manager only checks its health endpoint.

Official documentation: https://spiffe.io/docs/latest/deploying/spire_server/

FieldTypeDefaultDescriptionNotes
Health endpoint URL (health_url)url-Health endpoint URL of the existing service.required
Trust domain (trust_domain)string-Trust domain used by the platform.required

High availability​

Clusterreplicas (replication)
High availabilityexternal (external)
Failoverload balancer (load-balancer)
Replicationshared store (shared-store)
Quorumnone (none)
Discoverynone (none)
Entry pointload balancer (load-balancer)
Official documentationhttps://spiffe.io/docs/latest/planning/scaling_spire/

Prerequisites​

PrerequisiteMust be highly availableModesDescription
datastoreyeshaHighly available PostgreSQL shared by the servers (MySQL is also supported upstream).

Topology per mode​

ModesHighest catalog levelDistributionQuorum componentFault domainsDescription
standalonestandalone (standalone)single (single)-1One server with a local SQLite datastore, agents on any host.
haha (ha)active-active (active-active)-3Three servers sharing a PostgreSQL datastore; one agent per host.

Notes​

  • The agents keep serving the identities already issued while the servers are unreachable, until the certificates expire.

Configuration parameters​

Trust domain​

ParameterTypeDefaultAllowed valuesRequiredSecretRestartDescription
Trust domain (trust_domain)stringnavin.internal^[a-z0-9._-]+$yesnoyesSPIFFE trust domain (spiffe://<domain>/...).
CA lifetime (ca_ttl)duration24h-nononoLifetime of the signing CA of the servers.
SVID lifetime (svid_ttl)duration1h-nononoDefault lifetime of an X.509 SVID.

Network​

ParameterTypeDefaultAllowed valuesRequiredSecretRestartDescription
Server port (server_port)port8081-nonoyesgRPC port reached by the agents.
Bundle endpoint port (bundle_port)port8443-nonoyesHTTPS port serving the trust bundle to the agents at bootstrap (certificate of the manager CA).
Server health port (server_health_port)port8080-nononoPort of /live and /ready of the server.
Server metrics port (server_metrics_port)port9988-nononoPrometheus port of the server.
Agent health port (agent_health_port)port8089-nononoPort of /live and /ready of the agent.
Agent metrics port (agent_metrics_port)port9989-nononoPrometheus port of the agent.
Certificates of the manager CA (tls_enabled)booltrue-nonoyesIssue a certificate of the manager CA to every server and agent: the bundle endpoint serves it and the agents attest their node with it (x509pop). Keep it on: SPIRE does not start without these certificates.
Server address of the agents (server_address)string(empty)^([A-Za-z0-9.-]{1,253})?$nononoName of the load balancer in front of the SPIRE servers (ha mode), forwarding the server port; empty: the first server. The agents download the trust bundle from the first server at bootstrap only.

Logging​

ParameterTypeDefaultAllowed valuesRequiredSecretRestartDescription
Log level (log_level)enumINFODEBUG, INFO, WARN, ERRORnononoVerbosity of the server and agent logs.

Dependencies​

For each active dependency the Manager takes the first of: the binding chosen in the wizard; a service of the same installation that provides it; a service already installed in the cluster; the only connection of the expected type. Otherwise an optional dependency stays unbound, and a required one is added to the installation in its default mode (the column below names the catalog service added).

BindingProvided byConnection typeEndpointOptionalWhen nothing is boundDescription
datastore (ha)postgresqlpostgresqlsqlnopostgresql is added to the installationShared datastore of the three SPIRE servers.

Endpoints​

EndpointSchemeComponentPortPathTLS parameterBinding parametersBinding secretsProvisioning command
servertcpspire-server8081 (server_port)-tls_enabled---

Client configuration files​

Files rendered for the client configuration download:

  • spire.env (client.env.j2)

Commands​

CommandComponentTargetDescription
Server health (healthcheck)spire-serverevery hostRuns spire-server healthcheck on every server.
List the agents (list_agents)spire-serverfirst hostLists the attested agents.

Health checks​

Liveness (per instance)​

ComponentCheckDetails
spire-serverHTTP http://127.0.0.1:{{ config.server_health_port }}/readyExpected 200; 30 retries; interval 2 s; timeout 3 s
spire-agentHTTP http://127.0.0.1:{{ config.agent_health_port }}/readyExpected 200; 30 retries; interval 2 s; timeout 3 s

Preflight checks​

CheckTypeMeaningSeverityComponents
server_port_freeport_free {"param": "server_port"}port 8081 free on the hostblockingspire-server
time_synctime_sync {}a synchronized clockblockingevery component

Uninstall​

Paths removed when the data is purged: {{ paths.data }}, {{ paths.log }}.

Upstream documentation​