Current Behavior

Currently, the gateway has a limitation of 100 characters for a route name. This is applied to all routes, either they are created by the ingress controller or not.

Expected Behavior

When creating an ingress route with a route name of less than 100 characters, the route should be accepted and working

Error Logs

Kubernetes Resources with route names less than 100 characters, will NOT always be able to be processed. This happens because in Kubernetes, the route names are automatically concatenated with the namespace, and the name of the resource.

That creates impossible situations, confusion, and vague situations, since developers and devops cannot foresee in advance how much the route name will take under the hood.

Steps to Reproduce

• Create a setup with Apisix Ingress Controller
• Create a route with 99 characters as one of the route names (to be sure)
• Apply.
• Watch the Ingress throw errors due to validation issues.

Environment

• All versions of Apisix
• Kubernetes (any version)

Question

Is there any reason why there is a limit of 100 characters in the route name in the first place? I have a PR ready, I don't know if it's the correct way of solving, this - but when this happens, it's affecting everyone using the cluster.