You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
### Node ports handling during upgrade from MKE 3 to MKE 4
|MKE 3 NodePort Range | Ingress Controller in MKE 3 | Ingress NodePorts in MKE 4 |
|----------------------|-----------------------------|---------------------------------------------------------------------------------------------|
|Default | Enabled | Uses the same ports set by the user in MKE 3 |
|Default | Disabled | Default ports: HTTP: 33000, HTTPS: 33001 |
|Custom | Enabled | Uses the same ports set by the user in MKE 3 |
|Custom | Disabled | Reserves the first two static ports from the NodePort range for the ingress controller |
<callout> The static NodePort range is calculated based on the guidance from [Kubernetes blog on NodePort dynamic and static allocation](https://kubernetes.io/blog/2023/05/11/nodeport-dynamic-and-static-allocation/#how-can-you-avoid-nodeport-service-port-conflicts). </callout>
For instance, if the NodePort range is `30000-32767`, the NodePorts for the ingress controller will be `30000` and `30001`.
The text was updated successfully, but these errors were encountered: