Skip to content

OCPBUGS-18537: (Release note) ingressClassName is required for all ingress objects #87421

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

Merged
merged 1 commit into from
Feb 4, 2025
Merged

OCPBUGS-18537: (Release note) ingressClassName is required for all ingress objects #87421

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions release_notes/ocp-4-12-release-notes.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -705,6 +705,11 @@ In {product-title} 4.12, the External DNS Operator modifies the format of the Ex

The upstream version of `ExternalDNS` for {product-title} 4.12 is v0.13.1.

[id="ocp-4-12-ingressclassname-ingressClassName-required_{context}"]
==== The ingressClassName field is required for each ingress object

Beginning with {product-title} 4.12, you must specify a class name in the `ingressClassName` field for each ingress object to ensure proper routing and functionality.

[id="ocp-4-12-nw-metrics-telemetry_{context}"]
==== Capturing metrics and telemetry associated with the use of routes and shards

Expand Down