OSDOCS-18770 Document the removal of restriction on Gateway API x-k8s… #109141
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,18 @@ | ||
| :_mod-docs-content-type: REFERENCE | ||
| [id="rn-ocp-release-notes-notable-changes_{context}"] | ||
| = Notable technical changes | ||
|
Collaborator
There was a problem hiding this comment. 🤖 [error] AsciiDocDITA.ShortDescription: Assign [role="_abstract"] to a paragraph to use it as in DITA. |
||
|
|
||
| This section includes several technical changes for {product-title} {product-version}. | ||
|
|
||
| //// | ||
| Instructions: Add entries in the following format: | ||
|
|
||
| Item description:: | ||
| + | ||
| Detailed information. | ||
| //// | ||
|
|
||
| Gateway API `x-k8s.io` group CRDs are no longer restricted:: | ||
| + | ||
| In previous versions of {product-title}, deploying Gateway API custom resource definitions (CRDs) that belong to the `x-k8s.io` group was blocked. Starting in {product-title} {product-version}, this restriction is removed, and you can deploy Gateway API CRDs that belong to the `x-k8s.io` group, such as `gateway.networking.x-k8s.io`. Experimental CRDs in the `gateway.networking.k8s.io` group remain restricted. For more information, see xref:../networking/ingress_load_balancing/configuring_ingress_cluster_traffic/ingress-gateway-api.adoc#nw-ingress-gateway-api-implementation_ingress-gateway-api[Gateway API implementation for {product-title}]. | ||
|
Collaborator
There was a problem hiding this comment. 🤖 [error] OpenShiftAsciiDoc.NoXrefInModules: Do not include xrefs in modules, only assemblies (exception: release notes modules). |
||
|
|
||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
one question/suggestion: we allow deploying this group, but it doesn't mean we will reconcile it. Is there a good way of saying "these APIs will still be ignored by our Gateway API implementation and can be used by 3rd party implementations" ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rikatz I'll look and see!