Repository navigation
Update SPIRE tutorial images and Go security patches - #147
Open
keeganwitt wants to merge 2 commits into
Open
keeganwitt wants to merge 2 commits into
keeganwitt wants to merge 2 commits into
Conversation
Signed-off-by: Keegan Witt <keeganwitt@gmail.com>
Signed-off-by: Keegan Witt <keeganwitt@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Use SPIRE 1.15.5 for the pinned tutorial images and Go 1.26.10 for CI and the nested demo toolchain. SPIRE 1.15.5 is the published security release built with Go 1.26.10: https://github.com/spiffe/spire/releases/tag/v1.15.5
This propagates the eMudhra certificate-verification mitigation (CVE-2026-111943). The usual private SPIFFE trust paths are precautionary updates; public-root federation, bootstrap, or cloud integrations can have conditional exposure. This does not establish an exploitable tutorial deployment.
Validation: all changed YAML parses, all 23 pinned SPIRE image references resolve to 1.15.5 in source, and
git diff --checkpasses. Cluster/container integration tests were not run locally.Go certificate-verification mitigation: https://pkg.go.dev/vuln/GO-2026-6809.
CI follow-up: the previous run timed out because shared Envoy setup used unbounded rollout waits while nested scripts suppressed startup output. The follow-up performs one bounded rollout check per SPIRE resource and emits pod descriptions/events and server/agent logs on failure. It also surfaces nested setup progress.
Validation for this follow-up: mocked ready, server-rollout failure, agent-rollout failure, and missing-attestation cases passed; the original baseline fails the regression check; Bash syntax checks passed for all three changed scripts; git diff --check passed. The actual pod readiness cause remains unverified. New run https://github.com/spiffe/spire-tutorials/actions/runs/42494656432 is action_required with no jobs started, so cluster diagnostics await maintainer workflow approval. The local Docker daemon is unavailable.