Upgrade ingress-nginx chart to 4.11.2 and app to 1.11.2

[davidumea]

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

Release notes

Drops support for Kubernetes v1.25, adds support for Kubernetes v1.30.
Nginx version upgrade to 1.25.5.

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

Upgrades ingress-nginx to chart version 4.11.2 and app version 1.11.2.
Also exposed topologySpreadConstraints for default backend to apps config since this was also exposed in upstream values.

• Fixes [2] Upgrade Ingress-nginx to newer version #2163

Information to reviewers

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 upgrades CRDs
  • The change updates the config and the schema
• 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 are not affected)
  • The metrics names did change (Grafana dashboards and Prometheus alerts were fixed)
• Logs checks:
  • The logs do not show any errors after the change
• Pod Security Policy checks:
  • Any changed pod is covered by Pod Security Admission
  • Any changed pod is covered by Gatekeeper Pod Security Policies
  • The change does not cause any pods to be blocked by Pod Security Admission or Policies
• Network Policy 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

[OlleLarsson]

Any notable changes between ingress-nginx 1.9 and 1.11?
Annotation changes, nginx version, or similar?

[davidumea]

Any notable changes between ingress-nginx 1.9 and 1.11? Annotation changes, nginx version, or similar?

Nginx version is updated from 1.21.6 to 1.25.5, I looked through the changelog and I don't think that any of the changes will affect us.

Yes some annotation changes were made, SSLv2, SSLv3, TLSv1 & TLSv1.1 support was dropped. I guess I should add a platform administrator notice for this?

[davidumea]

Yes some annotation changes were made, SSLv2, SSLv3, TLSv1 & TLSv1.1 support was dropped. I guess I should add a platform administrator notice for this?

Nevermind, that was just a cleanup PR, support for TLS v1.0 and v1.1 was already dropped since earlier.