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
The function used from the Kubernetes validation library to validate DNS addresses during the preflight check for load balancer addresses imposes an unintended 63-character limit. This limit stems from the validation criteria used for pod/service DNS names, but in the case of load balancer addresses, the specified address can be up to 255 characters. The validation should allow for the full 255-character length rather than being capped at 63 characters.
Expected Behavior
Compliant DNS addresses are respected in the tcpLoadBalancer collector
Steps To Reproduce
Run a preflight check for a load balancer address using an address longer than 63 characters.
Observe that the validation fails despite the address being under the 255-character limit.
Additional Context
Include the following information.
Troubleshoot version. If you built from source, note that including the version of Go you used to build with.
Operating system
Operating system version
Other details that might be helpful in diagnosing the problem
Troubleshoot v0.103.0
The text was updated successfully, but these errors were encountered:
Bug Description
The function used from the Kubernetes validation library to validate DNS addresses during the preflight check for load balancer addresses imposes an unintended 63-character limit. This limit stems from the validation criteria used for pod/service DNS names, but in the case of load balancer addresses, the specified address can be up to 255 characters. The validation should allow for the full 255-character length rather than being capped at 63 characters.
Expected Behavior
Compliant DNS addresses are respected in the
tcpLoadBalancer
collectorSteps To Reproduce
Additional Context
Include the following information.
Troubleshoot version. If you built from source, note that including the version of Go you used to build with.
Operating system
Operating system version
Other details that might be helpful in diagnosing the problem
Troubleshoot v0.103.0
The text was updated successfully, but these errors were encountered: