-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Reverts changes made to udn table 4.17 #109015
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.
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
Open
stevsmit
wants to merge
1
commit into
openshift:enterprise-4.17
Choose a base branch
from
stevsmit:udn-table-417
base: enterprise-4.17
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,49 @@ | ||
| //module included in the following assembly: | ||
| // | ||
| // *networking/multiple_networks/understanding-user-defined-networks.adoc | ||
|
|
||
| :_mod-docs-content-type: REFERENCE | ||
| [id="nw-udn-additional-config-details_{context}"] | ||
| == Additional configuration details for a UserDefinedNetworks CR | ||
|
|
||
| [role="_abstract"] | ||
| Configure optional advanced settings for `ClusterUserDefinedNetwork` and `UserDefinedNetwork` CRs when default values conflict with your network topology or when you need persistent IP addresses, custom gateways, or specific subnet configurations. | ||
|
|
||
| It is not recommended to set these fields without explicit need and understanding of OVN-Kubernetes network topology. | ||
|
|
||
| . Optional configurations for user-defined networks | ||
| [cols="2,1,7", options="header"] | ||
| |==== | ||
|
|
||
| |*CUDN field*|*UDN field*|*Type*|*Description* | ||
|
|
||
| |`spec.network.<topology>.joinSubnets` | ||
| |`spec.<topology>.joinSubnets` | ||
| |object | ||
| |When omitted, the platform sets default values for the `joinSubnets` field of `100.65.0.0/16` for IPv4 and `fd99::/64` for IPv6. If the default address values are used anywhere in the cluster's network you must override it by setting the `joinSubnets` field. If you choose to set this field, ensure it does not conflict with other subnets in the cluster such as the cluster subnet, the `default` network cluster subnet, and the masquerade subnet. | ||
|
|
||
| The `joinSubnets` field configures the routing between different segments within a user-defined network. Dual-stack clusters can set 2 subnets, one for each IP family; otherwise, only 1 subnet is allowed. This field is only allowed for the `Primary` network. | ||
|
|
||
| |`spec.network.<topology>.ipam.lifecycle` | ||
| |`spec.<topology>.ipam.lifecycle` | ||
| |object | ||
| |The `spec.ipam.lifecycle` field configures the IP address management system (IPAM). You might use this field for virtual workloads to ensure persistent IP addresses. The only allowed value is `Persistent`, which ensures that your virtual workloads have persistent IP addresses across reboots and migration. These are assigned by the container network interface (CNI) and used by OVN-Kubernetes to program pod IP addresses. You must not change this for pod annotations. | ||
|
|
||
| Setting a value of Persistent is only supported when `ipam.mode` parameter is set to `Enabled`. | ||
|
|
||
| |`spec.network.<topology>.ipam.mode` | ||
| |`spec.network.<topology>.ipam.mode` | ||
| |object | ||
| a|The `mode` parameter controls how much of the IP configuration is managed by OVN-Kubernetes. The following options are available: | ||
| * `Enabled`: When enabled, OVN-Kubernetes applies the IP configuration to the SDN infrastructure and assigns IP addresses from the selected subnet to the individual pods. This is the default setting. When set to `Enabled`, the `subnets` field must be defined. `Enabled` is the default configuration. | ||
| * `Disabled`: When disabled, OVN-Kubernetes only assigns MAC addresses and provides layer 2 communication, which allows users to configure IP addresses. `Disabled` is only available for layer 2 (secondary) networks. By disabling IPAM, features that rely on selecting pods by IP, for example, network policy, services, and so on, no longer function. Additionally, IP port security is also disabled for interfaces attached to this network. The `subnets` field must be empty when `spec.ipam.mode` is set to `Disabled.` | ||
|
|
||
| |`spec.network.<topology>.mtu` | ||
| |`spec.<topology>.mtu` | ||
| |integer | ||
| |The maximum transmission units (MTU). The default value is `1400`. The boundary for IPv4 is `576`, and for IPv6 it is `1280`. | ||
| |==== | ||
|
|
||
| where: | ||
|
|
||
| `<topology>`:: Is one of `layer2` or `layer3`. |
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,50 @@ | ||
| //module included in the following assembly: | ||
| // | ||
| // *networking/multiple_networks/understanding-user-defined-networks.adoc | ||
|
|
||
| :_mod-docs-content-type: REFERENCE | ||
| [id="nw-udn-additional-config-details_{context}"] | ||
| == Additional configuration details for a UserDefinedNetworks CR | ||
|
|
||
| The following table explains additional configurations for UDN that are optional. It is not recommended to set these fields without explicit need and understanding of OVN-Kubernetes network topology. | ||
|
|
||
| . Optional configurations for user-defined networks | ||
| [cols="2,1,7", options="header"] | ||
| |==== | ||
|
|
||
| |CUDN field|UDN field|Type|Description | ||
|
|
||
| |`spec.network.<topology>.joinSubnets` | ||
| |`spec.<topology>.joinSubnets` | ||
| |object | ||
| |When omitted, the platform sets default values for the `joinSubnets` field of `100.65.0.0/16` for IPv4 and `fd99::/64` for IPv6. If the default address values are used anywhere in the cluster's network you must override it by setting the `joinSubnets` field. If you choose to set this field, ensure it does not conflict with other subnets in the cluster such as the cluster subnet, the `default` network cluster subnet, and the masquerade subnet. | ||
|
|
||
| The `joinSubnets` field configures the routing between different segments within a user-defined network. Dual-stack clusters can set 2 subnets, one for each IP family; otherwise, only 1 subnet is allowed. This field is only allowed for the `Primary` network. | ||
|
|
||
| |`spec.network.<topology>.ipam.lifecycle` | ||
| |`spec.<topology>.ipam.lifecycle` | ||
| |object | ||
| |The `spec.ipam.lifecycle` field configures the IP address management system (IPAM). You might use this field for virtual workloads to ensure persistent IP addresses. The only allowed value is `Persistent`, which ensures that your virtual workloads have persistent IP addresses across reboots and migration. These are assigned by the container network interface (CNI) and used by OVN-Kubernetes to program pod IP addresses. You must not change this for pod annotations. | ||
|
|
||
| Setting a value of Persistent is only supported when `ipam.mode` parameter is set to `Enabled`. | ||
|
|
||
| |`spec.network.<topology>.ipam.mode` | ||
| |`spec.network.<topology>.ipam.mode` | ||
| |object | ||
| |The `mode` parameter controls how much of the IP configuration is managed by OVN-Kubernetes. The following options are available: | ||
|
|
||
| **Enabled:** + | ||
| When enabled, OVN-Kubernetes applies the IP configuration to the SDN infrastructure and assigns IP addresses from the selected subnet to the individual pods. This is the default setting. When set to `Enabled`, the `subnets` field must be defined. `Enabled` is the default configuration. | ||
|
|
||
| **Disabled:** + | ||
| When disabled, OVN-Kubernetes only assigns MAC addresses and provides layer 2 communication, which allows users to configure IP addresses. `Disabled` is only available for layer 2 (secondary) networks. By disabling IPAM, features that rely on selecting pods by IP, for example, network policy, services, and so on, no longer function. Additionally, IP port security is also disabled for interfaces attached to this network. The `subnets` field must be empty when `spec.ipam.mode` is set to `Disabled.` | ||
|
|
||
| |`spec.network.<topology>.mtu` | ||
| |`spec.<topology>.mtu` | ||
| |integer | ||
| |The maximum transmission units (MTU). The default value is `1400`. The boundary for IPv4 is `576`, and for IPv6 it is `1280`. | ||
| |==== | ||
|
|
||
| where: | ||
|
|
||
| `<topology>`:: Is one of `layer2` or `layer3`. |
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
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.
🤖 [error] AsciiDocDITA.DocumentTitle: The document title (a level 0 heading) is missing.