Skip to content
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

Jump to bottom

cni-2 updates #116

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

cni-2 updates #116

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6963093
cni-2 updates
vikramhh Oct 2, 2024
d03bba7
make range inclusive
vikramhh Oct 2, 2024
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
10 changes: 5 additions & 5 deletions content/docs/concepts/cni.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -81,7 +81,6 @@ The following table includes details on all of the configurable `network` fields
| Field | Description | Values | Default |
|-------|-------------|--------|----------|
| `serviceCIDR` | Sets the IPv4 range of IP addresses for services in a Kubernetes cluster. | Valid IPv4 CIDR | `10.96.0.0/16` |
| `nodePortRange` | Sets the allowed port range for Kubernetes services of the NodePort type. | Valid port range | `32768-35535` |
| `providers` | Sets the provider for the active CNI. | `calico` | `calico` |

## Providers configuration
Expand All @@ -102,7 +101,8 @@ for the Calico provider.

[^0]: For the available values, consult your provider documentation.

## Limitations

Components using `nodeports` may have their own specific way of specifying the port numbers for NodePorts,
and these may need to be changed simultaneusly with the `nodePortRange`.
## Notes
mke4 uses a static port range for k8s nodeports [32768-35535].
upgrade from mke3 to mke4 is only supported for clusters using the default k8s proxier (iptables)
only kdd backed mke3 clusters are supported for upgrading to mke4
once mke3 is successfully upgraded to mke4, it displays a list of ports that are no longer required to be opened on manager and/or worker nodes and could be blocked
Comment on lines +104 to +108
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
## Notes
mke4 uses a static port range for k8s nodeports [32768-35535].
upgrade from mke3 to mke4 is only supported for clusters using the default k8s proxier (iptables)
only kdd backed mke3 clusters are supported for upgrading to mke4
once mke3 is successfully upgraded to mke4, it displays a list of ports that are no longer required to be opened on manager and/or worker nodes and could be blocked
{{< callout type="note" >}}
- MKE 4 uses a static port range for Kubernetes NodePorts, from `32768` to `35535`.
- Only clusters that use the the default Kubernetes proxier `iptables` can be upgraded from MKE 3 to MKE 4.
- Only KDD-backed MKE 3 clusters can be upgraded to MKE 4.
- Following a successful MKE 3 to MKE 4 upgrade, a list displays that presents the ports that no longer need to be opened on manager or worker nodes. These ports can be blocked.
{{< /callout >}}