Apply better wording to remain current in future versions

Co-authored-by: Tim Bannister <[email protected]>
Signed-off-by: Paul "TBBle" Hampson <[email protected]>

Author: TBBle

content/en/docs/concepts/services-networking/service.md

@@ -692,8 +692,12 @@ that route traffic directly to pods as opposed to using node ports. By default,
 is `true` and type LoadBalancer Services will continue to allocate node ports. If `spec.allocateLoadBalancerNodePorts`
 is set to `false` on an existing Service with allocated node ports, those node ports will NOT be de-allocated automatically.
 You must explicitly remove the `nodePorts` entry in every Service port to de-allocate those node ports.
-You must enable the `ServiceLBNodePortControl` feature gate to use this field in v1.20 and v1.21,
-and the feature gate is enabled by default from v1.22 onwards.
+Your cluster must have the `ServiceLBNodePortControl`
+[feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
+enabled to use this field.
+For Kubernetes v{{< skew currentVersion >}}, this feature gate is enabled by default,
+and you can use the `spec.allocateLoadBalancerNodePorts` field. For clusters running
+other versions of Kubernetes, check the documentation for that release.
 
 #### Specifying class of load balancer implementation {#load-balancer-class}