Skip to content

Latest commit

 

History

History
43 lines (30 loc) · 1.59 KB

README.md

File metadata and controls

43 lines (30 loc) · 1.59 KB
Raw

Upgrade Suite

Description

This suite tests a simple upgrade step from SPIRE from one version to the next.

It does the following in order:

  1. Brings up the old SPIRE server and agent
  2. Obtains an SVID from the old agent
  3. Upgrades the SPIRE server
  4. Obtains an SVID from the old agent (making sure it has rotated)
  5. Upgrades the SPIRE agent
  6. Obtains an SVID from the new agent (making sure it has rotated)

Upgrading SPIRE Server/Agent

The upgrade is performed by bringing down the container running the old version and starting the container running the new version. The containers share configuration and data directory via a series of shared volumes.

Checking for rotation

To check for rotation, the SVID is written to disk at each step. It is then checked against the SVID for the previous step to make sure it has been rotated.

Maintenance

When making a SPIRE release, the versions.txt should be updated to add the new version, ideally as part of the first commit after release that bumps the base version in pkg/common/version/version.go.

When preparing to release a new "major" release (minor release pre-1.0), the versions.txt file should be updated to remove the "major"-2 versions, since we only support upgrading from one "major" build to the next. For example, if the versions.txt file contained all 0.8.x and 0.9.x versions, the 0.8.x versions should be removed as part of the 0.10.0 release.

Future considerations

  • Provide additional "+/- 1" SPIRE compatibility checks, as currently we only test that the SPIRE components start up and that SVIDs rotate.