Remove needless mention of previous versions
Co-authored-by: Tim Bannister <tim@scalefactory.com> Signed-off-by: Paul "TBBle" Hampson <Paul.Hampson@Pobox.com>
This commit is contained in:
		
							parent
							
								
									b54cee1c44
								
							
						
					
					
						commit
						be07879592
					
				|  | @ -686,7 +686,7 @@ The set of protocols that can be used for LoadBalancer type of Services is still | ||||||
| 
 | 
 | ||||||
| {{< feature-state for_k8s_version="v1.22" state="beta" >}} | {{< feature-state for_k8s_version="v1.22" state="beta" >}} | ||||||
| 
 | 
 | ||||||
| Starting in v1.20, you can optionally disable node port allocation for a Service Type=LoadBalancer by setting | You can optionally disable node port allocation for a Service of `type=LoadBalancer`, by setting | ||||||
| the field `spec.allocateLoadBalancerNodePorts` to `false`. This should only be used for load balancer implementations | the field `spec.allocateLoadBalancerNodePorts` to `false`. This should only be used for load balancer implementations | ||||||
| that route traffic directly to pods as opposed to using node ports. By default, `spec.allocateLoadBalancerNodePorts` | that route traffic directly to pods as opposed to using node ports. By default, `spec.allocateLoadBalancerNodePorts` | ||||||
| is `true` and type LoadBalancer Services will continue to allocate node ports. If `spec.allocateLoadBalancerNodePorts` | is `true` and type LoadBalancer Services will continue to allocate node ports. If `spec.allocateLoadBalancerNodePorts` | ||||||
|  |  | ||||||
		Loading…
	
		Reference in New Issue