CuraDevOps

tag: Eol · 4 items

2026-10-12 · Releases: envoy · source ↗ #envoy#service-mesh#eol
  • Platform/SRE — Act: Envoy 1.36 reaches end-of-life on 2026-10-14 — apply v1.36.13 now (includes CVE-2026-54786 wasm fix and three race-condition fixes) and immediately begin upgrading to a supported Envoy minor version before that date.
  • CI/CD — Skip
  • Leader — Skip
  • Signals: Envoy 1.36 reaches EOL in 2d (2026-10-14) · CVE-2026-54786 — CISA KEV: not listed, EPSS 0.00
2026-08-21 · GitLab Blog · source ↗ #gitlab#minor-release#eol
  • Platform/SRE — Plan: Teams self-hosting GitLab should plan an upgrade to 19.3 and note that it reaches EOL on 2026-11-19, meaning another upgrade cycle must be scheduled within the quarter to stay on a supported version.
  • CI/CD — Plan: Review the 19.3 release notes for any pipeline syntax, runner, or artifact-handling changes; schedule adoption before the 2026-11-19 EOL to avoid running unsupported GitLab CI infrastructure.
  • Leader — Skip
  • Signals: GitLab 19.3 reaches EOL in 90d (2026-11-19)
2026-08-17 · Releases: containerd · source ↗ #containerd#container-runtime#eol
  • Platform/SRE — Plan: containerd 2.2 reaches EOL on 2026-11-06 (81 days), so plan migration to a supported branch before then; also note this patch disables checkpoint restore in CreateContainer by default, which may break CRIU-based workloads that haven’t set enable_experimental_restore_via_create.
  • CI/CD — Skip
  • Leader — Skip
  • Signals: containerd 2.2 reaches EOL in 81d (2026-11-06) · deprecation mentioned (no explicit date found)
2026-07-10 · CNCF Blog · source ↗ #ingress-nginx#kubernetes#eol
  • Platform/SRE — Act: ingress-nginx reached end-of-life in March 2026 (now four months past); remaining on it means exposure to unpatched CVEs in a critical ingress path with no upstream fixes coming. Audit clusters for ingress-nginx usage and complete migration to a maintained alternative (Envoy Gateway, Ingress-NGINX from F5, Traefik) immediately.
  • CI/CD — Skip
  • Leader — Act: The SIG Network ingress-nginx controller is retired, making any org standardized on it subject to growing unpatched CVE exposure with no remediation path; this warrants a brief to leadership and a decision on a replacement ingress standard before the vulnerability surface widens further.
  • Signals: deprecation mentioned (no explicit date found)