Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Permanent issue - Breaking changes documentations #10186

Open
rikatz opened this issue Jul 6, 2023 · 2 comments
Open

Permanent issue - Breaking changes documentations #10186

rikatz opened this issue Jul 6, 2023 · 2 comments
Labels
kind/deprecation Categorizes issue or PR as related to a feature/enhancement marked for deprecation. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@rikatz
Copy link
Contributor

rikatz commented Jul 6, 2023 •
edited

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.11 - 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

TBD

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
@rikatz rikatz added the kind/feature Categorizes issue or PR as related to a new feature. label Jul 6, 2023
@k8s-ci-robot k8s-ci-robot added needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-priority triage/accepted Indicates an issue or PR is ready to be actively worked on. kind/deprecation Categorizes issue or PR as related to a feature/enhancement marked for deprecation. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jul 6, 2023
@rikatz rikatz removed the kind/feature Categorizes issue or PR as related to a new feature. label Jul 6, 2023
@k8s-ci-robot k8s-ci-robot added priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. and removed needs-priority labels Jul 6, 2023
@kubernetes kubernetes locked and limited conversation to collaborators Jul 6, 2023
@strongjz strongjz pinned this issue Jul 6, 2023
@rikatz
Copy link
Contributor Author

rikatz commented Oct 2, 2023

Added GeoIP deprecation to the list

@rikatz
Copy link
Contributor Author

rikatz commented Oct 10, 2023

Added #10498 for dropping support of architectures on v1.10

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
kind/deprecation Categorizes issue or PR as related to a feature/enhancement marked for deprecation. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
[sig-network] Ingress-Nginx
Status: No status
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rikatz @k8s-ci-robot