Skip to content

apps: upgrade ingress-nginx controller to 4.13.7 and chart to 1.13.7#2922

Open
kristiangronas wants to merge 1 commit intoelastisys:release-0.50from
railcp:for-upstream
Open

apps: upgrade ingress-nginx controller to 4.13.7 and chart to 1.13.7#2922
kristiangronas wants to merge 1 commit intoelastisys:release-0.50from
railcp:for-upstream

Conversation

@kristiangronas
Copy link
Copy Markdown
Contributor

Warning

This is a public repository, ensure not to disclose:

  • personal data beyond what is necessary for interacting with this pull request, nor
  • business confidential information, such as customer names.

What kind of PR is this?

Required: Mark one of the following that is applicable:

  • kind/feature
  • kind/improvement
  • kind/deprecation
  • kind/documentation
  • kind/clean-up
  • kind/bug
  • kind/other

Optional: Mark one or more of the following that are applicable:

Important

Breaking changes should be marked kind/admin-change or kind/dev-change depending on type
Critical security fixes should be marked with kind/security

  • kind/admin-change
  • kind/dev-change
  • kind/security
  • [kind/adr](set-me)

What does this PR do / why do we need this PR?

Fixes a high-severity CVE, and ingress-nginx has clusterwide secret access

  • Fixes #

Information to reviewers

This upgrade mitigates several CVE's have been announced before ingress-nginx's official retirement, including secret disclosure https://discuss.kubernetes.io/t/security-advisory-multiple-issues-in-ingress-nginx/34115

Security notice

Checklist

  • Proper commit message prefix on all commits
  • Change checks:
    • The change is transparent
    • The change is disruptive
    • The change requires no migration steps
    • The change requires migration steps
    • The change updates CRDs
    • The change updates the config and the schema
  • Documentation checks:
  • Metrics checks:
    • The metrics are still exposed and present in Grafana after the change
    • The metrics names didn't change (Grafana dashboards and Prometheus alerts required no updates)
    • The metrics names did change (Grafana dashboards and Prometheus alerts required an update)
  • Logs checks:
    • The logs do not show any errors after the change
  • PodSecurityPolicy checks:
    • Any changed Pod is covered by Kubernetes Pod Security Standards
    • Any changed Pod is covered by Gatekeeper Pod Security Policies
    • The change does not cause any Pods to be blocked by Pod Security Standards or Policies
  • NetworkPolicy checks:
    • Any changed Pod is covered by Network Policies
    • The change does not cause any dropped packets in the NetworkPolicy Dashboard
  • Audit checks:
    • The change does not cause any unnecessary Kubernetes audit events
    • The change requires changes to Kubernetes audit policy
  • Falco checks:
    • The change does not cause any alerts to be generated by Falco
  • Bug checks:
    • The bug fix is covered by regression tests

@kristiangronas kristiangronas requested review from a team as code owners February 3, 2026 16:32
@Eliastisys
Copy link
Copy Markdown
Contributor

Hello! Thank you for the contribution. Unfortunately this PR will not be merged as (stated in the main README) this repository is deprecated and will not get any further releases.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants