fix: pin e2e coraza-waf to a pullable fixed image#264
Merged
Conversation
The downstream gateway e2e config pinned the WAF filter as the bare tag `coraza-waf:v1.1.1-dev2`, which has no registry and cannot be pulled in CI, and predates the TPP Enforce listener-reject / response-phase fixes. The Envoy listener never programs (Programmed=Unknown), so the `trafficprotectionpolicy-enforce-serves-traffic` chainsaw test fails on main and gates every PR. Point the initContainer at the published, fixed image. Key changes: - Pin coraza-waf initContainer to ghcr.io/datum-labs/coraza-envoy-go-filter/coraza-waf:v1.3.0-alpha10
kevwilliams
approved these changes
Jul 13, 2026
This was referenced Jul 13, 2026
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
2 participants
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.
What
Point the downstream-gateway e2e coraza-waf initContainer at a real, published,
fixed image:
Why
The old pin was a bare tag (
coraza-waf:v1.1.1-dev2) — no registry, so CIcan't pull it — and predates the TPP Enforce fixes. The downstream Envoy
listener never programs:
So
chainsaw/trafficprotectionpolicy-enforce-serves-trafficfails onmainand gates every open PR (the whole
E2E Testsworkflow is red).v1.3.0-alpha10carries the response-phase / listener fixes tracked in theedge repo (https://github.com/datum-cloud/infra/issues/3319,
https://github.com/datum-cloud/infra/issues/3324,
https://github.com/datum-cloud/infra/issues/3329).
Verification
E2E Testsgreentrafficprotectionpolicy-enforce-serves-trafficpasses; downstream GatewayProgrammed=TrueTracked by #263. Root bug #242.