Skip to content

Add Traefik v2.x/v3.x backwards compatibility for IP allowlist Middleware#309

Open
Josh Blasbalg (jmb11111) wants to merge 1 commit intomainfrom
traefik-ipallowlist-backwards-compat
Open

Add Traefik v2.x/v3.x backwards compatibility for IP allowlist Middleware#309
Josh Blasbalg (jmb11111) wants to merge 1 commit intomainfrom
traefik-ipallowlist-backwards-compat

Conversation

@jmb11111
Copy link
Contributor

@jmb11111 Josh Blasbalg (jmb11111) commented Mar 16, 2026

Summary

  • The Traefik Middleware CRD uses different field names between versions: ipWhiteList (v2.x) and ipAllowList (v3.x)
  • Updated all IP allowlist Middleware templates to include both fields for cross-version compatibility
  • Matches the dual-field pattern implemented in terraform-modules for helm_prometheus (see snowplow-devops/terraform-modules#11200)

Changes

  • charts/service-deployment (0.34.0 → 0.35.0): Add ipAllowList alongside existing ipWhiteList
  • charts/snowplow-iglu-server (0.14.0 → 0.15.0): Same change
  • charts/common (0.4.0 → 0.5.0): Same change (used by multi-service-deployment)

Test plan

  • helm template renders Middleware with both ipWhiteList and ipAllowList fields
  • Deployed test release to sp-aws-sandbox-dev1 cluster (Traefik v2.11.38), verified Middleware CRD accepted both fields
  • Traefik v2/v3 field compatibility already validated in terraform-modules#11200 (confirmed v2.11.30 reads ipWhiteList and ignores unknown ipAllowList)

@jmb11111 Josh Blasbalg (jmb11111) force-pushed the traefik-ipallowlist-backwards-compat branch from 337c908 to 0d5458f Compare March 16, 2026 18:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants