Skip to content

Permanent issue - Breaking changes documentations #10186

@rikatz

Description

@rikatz

This issue is a permanent issue that will document breaking changes between every minor and major release. Maintainers will update it so we can track changes. The community can sign/get notifications of this issue.

v1.12 - To be released

Flags changes

Configmap changes

  • allow-cross-namespace-resources - should be disabled by default. Annotations below may be impacted:
    • auth-secret
    • auth-proxy-set-header
    • auth-tls-secret
    • fastcgi-params-configmap
    • proxy-ssl-secret
  • strict-validate-path-type - should be enabled by default
  • annotations-risk - should be lowered from Critical to High

Features removed

v1.10 - Completed

This version now uses NGINX v1.25

Features removed

  • OpenTracing, Zipkin, Jaeger and Datadog specific collectors - Ingress NGINX will support Opentelemetry only
  • legacy GeoIP - Users should use GeoIP2
  • Support for PodSecurityPolicy

v1.9 - Completed

Features removed

Configmap changes

Annotation changes

  • whitelist-source-range was renamed to allowlist-source-range. The former annotation still works but may be removed on a future release
  • All the annotations now have validation in place. This may represent breaking changes and should be monitored
  • custom-http-errors now supports only HTTP errors between 400 and 599
  • disable-annotation-validation - should default to false

Unplanned releases

Uncategorized breaking changes

  • Remove old SSL protocol and cipher support

Planned Features removed for v2.0.0

  • Modsecurity - should be replaced by Coraza
  • strict path validation to true
  • Move to the Control Plane/data plane architecture
  • removing Jaeger etc for Otel

Annotation changes

  • Remove whitelist-source-range annotation

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/deprecationCategorizes issue or PR as related to a feature/enhancement marked for deprecation.priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete.triage/acceptedIndicates an issue or PR is ready to be actively worked on.

    Type

    No type

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions