-
Notifications
You must be signed in to change notification settings - Fork 1.9k
OCPBUGS#6800: change the MTU in Local Zones deployments #55327
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
Conversation
|
@mtulio: This pull request references Jira Issue OCPBUGS-6800, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
Converting to draft as we need to validate the pop-up message and the impact when changing this. |
|
🤖 Updated build preview is available at: Build log: https://circleci.com/gh/ocpdocs-previewbot/openshift-docs/8347 |
1539ab4 to
d373e4e
Compare
|
@mtulio: This pull request references Jira Issue OCPBUGS-6800, which is invalid:
Comment DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
@mtulio: This pull request references Jira Issue OCPBUGS-6800, which is invalid:
Comment DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
mtulio
left a comment
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.
Adding the option to configure OpenShift SDN (not tested) and an "IMPORTANT" note.
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.
.
|
@kalexand-rh @GroceryBoyJr As you worked on the GA document, it would be nice to have your review here. Thanks! |
|
/assign @yunjiang29 @rvanderp3 |
|
@mtulio: This pull request references Jira Issue OCPBUGS-6800, which is invalid:
Comment DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/assign @makentenza |
|
/assign @zhaozhanqi |
|
/lgtm |
|
/cherrypick enterprise-4.13 |
|
/cherrypick enterprise-4.12 |
|
@adellape: new pull request created: #55789 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
@adellape: new pull request created: #55790 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
This change introduce to installer generate the CNO manifest file cluster-network-03-config.yml into the cluster manifest path. The goal is to force the Cluster Network to use MTU according to the network plugin when the AWS Edge machine pool is set. Currently there is support only for AWS Local Zones on edge machine pool. Local Zones limits the MTU for 1300[1] to communicate into the nodes in Availability Zones (regular zones within the region). On the Phase-0[2] of support of AWS Local Zones, the instructions is added in the documentation[3]. This change is covering the Phase-1[4]. [1] https://docs.aws.amazon.com/local-zones/latest/ug/how-local-zones-work.html [2] https://issues.redhat.com/browse/SPLAT-635 [3] openshift/openshift-docs#55327 [4] https://issues.redhat.com/browse/SPLAT-636
This change generates the CNO manifest file `cluster-network-03-config.yml` into the cluster manifest path. The goal is to force the Cluster Network to use MTU according to the network plugin when the AWS Edge machine pool is set. Currently, there is support only for AWS Local Zones on the edge machine pool. Local Zones limit the MTU to 1300[1] to communicate with the nodes in Availability Zones (regular zones within the region). In Phase-0[2] of support of AWS Local Zones, the instructions are added in the documentation[3]. This change is covering Phase-1[4]. [1] https://docs.aws.amazon.com/local-zones/latest/ug/how-local-zones-work.html [2] https://issues.redhat.com/browse/SPLAT-635 [3] openshift/openshift-docs#55327 [4] https://issues.redhat.com/browse/SPLAT-636
This change generates the CNO manifest file `cluster-network-03-config.yml` into the cluster manifest path. The goal is to force the Cluster Network to use MTU according to the network plugin when the AWS Edge machine pool is set. Currently, there is support only for AWS Local Zones on the edge machine pool. Local Zones limit the MTU to 1300[1] to communicate with the nodes in Availability Zones (regular zones within the region). In Phase-0[2] of support of AWS Local Zones, the instructions are added in the documentation[3]. This change is covering Phase-1[4]. [1] https://docs.aws.amazon.com/local-zones/latest/ug/how-local-zones-work.html [2] https://issues.redhat.com/browse/SPLAT-635 [3] openshift/openshift-docs#55327 [4] https://issues.redhat.com/browse/SPLAT-636
This change generates the CNO manifest file `cluster-network-03-config.yml` into the cluster manifest path. The goal is to force the Cluster Network to use MTU according to the network plugin when the AWS Edge machine pool is set. Currently, there is support only for AWS Local Zones on the edge machine pool. Local Zones limit the MTU to 1300[1] to communicate with the nodes in Availability Zones (regular zones within the region). In Phase-0[2] of support of AWS Local Zones, the instructions are added in the documentation[3]. This change is covering Phase-1[4]. [1] https://docs.aws.amazon.com/local-zones/latest/ug/how-local-zones-work.html [2] https://issues.redhat.com/browse/SPLAT-635 [3] openshift/openshift-docs#55327 [4] https://issues.redhat.com/browse/SPLAT-636
This change generates the CNO manifest file `cluster-network-03-config.yml` into the cluster manifest path. The goal is to force the Cluster Network to use MTU according to the network plugin when the AWS Edge machine pool is set. Currently, there is support only for AWS Local Zones on the edge machine pool. Local Zones limit the MTU to 1300[1] to communicate with the nodes in Availability Zones (regular zones within the region). In Phase-0[2] of support of AWS Local Zones, the instructions are added in the documentation[3]. This change is covering Phase-1[4]. [1] https://docs.aws.amazon.com/local-zones/latest/ug/how-local-zones-work.html [2] https://issues.redhat.com/browse/SPLAT-635 [3] openshift/openshift-docs#55327 [4] https://issues.redhat.com/browse/SPLAT-636
This change generates the CNO manifest file `cluster-network-03-config.yml` into the cluster manifest path. The goal is to force the Cluster Network to use MTU according to the network plugin when the AWS Edge machine pool is set. Currently, there is support only for AWS Local Zones on the edge machine pool. Local Zones limit the MTU to 1300[1] to communicate with the nodes in Availability Zones (regular zones within the region). In Phase-0[2] of support of AWS Local Zones, the instructions are added in the documentation[3]. This change is covering Phase-1[4]. [1] https://docs.aws.amazon.com/local-zones/latest/ug/how-local-zones-work.html [2] https://issues.redhat.com/browse/SPLAT-635 [3] openshift/openshift-docs#55327 [4] https://issues.redhat.com/browse/SPLAT-636
Version(s): 4.12+
Issue: https://issues.redhat.com/browse/OCPBUGS-6800
This PR changes the default MTU on the Day-0 guide for installing a cluster in existing VPC with AWS Local Zone subnets.
The MTU of 1200 should be the maximum allowed considering 1300 (from AWS Documentation to LZ nodes communicate with nodes in regular zones [parent region]) and 100 of OVN overhead.
Link to docs preview: https://55327--docspreview.netlify.app/openshift-enterprise/latest/installing/installing_aws/installing-aws-localzone.html#installation-localzone-generate-k8s-manifestinstalling-aws-localzone
QE review:
Additional information:
Required reviewers: