Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Istio 1.3 to Istio 1.4 Upgrade causes RouteConfigurationValidationError's. #19665
We currently run Istio v1.3.6 in our clusters, and things are working just fine, however when trying to upgrade to Istio v1.4.2 the Istio Pilot bombs out with the following error message, followed by ~40,000 lines worth of configuration.
I realize this is likely something on our side, but I'm not quite sure what, my best guess is it's something to do with the Envoy generated configuration shown below, particularly the
The matching Istio configuration for the VS looks like this, which works just fine in v1.3.6.
I could be way off on my analysis, but at current, this is my best guess. Could anybody point me in the right direction>
Upgrade to v1.4.2 from v1.3.6 is seamless.
Steps to reproduce the bug
We have thousands of routes, and VS's so it could really be anything, but I've posted my best guess above.
Version (include the output of
How was Istio installed?
The helm template method.
Environment where bug was observed (cloud vendor, OS, etc)
I applied the same config, with 1.4.2, and it correctly is sent to Envoy:
You can see its the same config as in the issue above. The weird
So I am not sure why envoy is complaining about missing path specifier when it is set...
@dominicgunn How did you obtain the above config? Specificically the 10 part.
It seems to me the envoy/istio-proxy cannot recognize the new field. So the printer prints the field number instead of field name.