Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RouteConfiguration rejected due to constraint validation failed on CorsPolicy #13358

Closed
sterchelen opened this issue Apr 16, 2019 · 7 comments

Comments

@sterchelen
Copy link
Contributor

commented Apr 16, 2019

Describe the bug
I have cors policy set. When I have two replicas of a gateway deployment, one of them has the following error message:

[2019-04-15 19:00:42.513][12][warning][config] [bazel-out/k8-opt/bin/external/envoy/source/common/config/_virtual_includes/grpc_mux_subscription_lib/common/config/grpc_mux_subscription_impl.h:77]
 gRPC config for type.googleapis.com/envoy.api.v2.RouteConfiguration rejected: Proto constraint validation failed 
(Using deprecated option 'envoy.api.v2.route.CorsPolicy.enabled' from file route.proto. This configuration will be removed from Envoy soon.
Please see https://www.envoyproxy.io/docs/envoy/latest/intro/deprecated for details. 
If continued use of this field is absolutely necessary, see https://www.envoyproxy.io/docs/envoy/latest/configuration/runtime#using-runtime-overrides-for-deprecated-features for how to apply a temporary and highly discouraged override.): allow_origin: "MYDOMAIN"

The one that has this message is not handling the traffic.

Expected behavior
Deprecated configuration should not reject proto constraint.

Version
1.1.0

Installation
With helm

Environment
GKE

@howardjohn

This comment has been minimized.

Copy link
Member

commented Apr 16, 2019

@kyessenov is this related to what you were working on with the RuntimeFractionalPercent stuff?

@esnible

This comment has been minimized.

Copy link
Contributor

commented Apr 16, 2019

@sterchelen Can you attach your Istio rule that caused Envoy to generate this message? I'd like to use it as a test case to improve Istio validation.

@kyessenov

This comment has been minimized.

Copy link
Contributor

commented Apr 16, 2019

1.1.3 has a patch to avoid using the deprecated field in Envoy. Although, I'm not sure how you ended up with 1.0.0 istio and a recent envoy in your set-up. I think the recommendation is to use a released version of istio,e.g. 1.1.3.

@sterchelen

This comment has been minimized.

Copy link
Contributor Author

commented Apr 16, 2019

@kyessenov, where do you see that I'm running two versions of istio?

@howardjohn

This comment has been minimized.

Copy link
Member

commented May 31, 2019

This issue has been fixed on 1.1.3+ I believe. If you have issues with newer versions please reopen this

@howardjohn howardjohn closed this May 31, 2019

@enmasse

This comment has been minimized.

Copy link

commented Sep 2, 2019

Do you have a workaround for this issue?

@howardjohn

This comment has been minimized.

Copy link
Member

commented Sep 2, 2019

using Istio 1.1.3+ is the only workaround as far as I know

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
5 participants
You can’t perform that action at this time.