RFE-2782/phase-1: Set MTU to CNI when edge pool is present on AWS #11
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.
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