-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
xds: enable the is_optional
field for HttpFilter
#16119
Conversation
Signed-off-by: He Jie Xu <hejie.xu@intel.com>
Signed-off-by: He Jie Xu <hejie.xu@intel.com>
…d config Signed-off-by: He Jie Xu <hejie.xu@intel.com>
Signed-off-by: He Jie Xu <hejie.xu@intel.com>
Signed-off-by: He Jie Xu <hejie.xu@intel.com>
Signed-off-by: He Jie Xu <hejie.xu@intel.com>
if (Runtime::runtimeFeatureEnabled( | ||
"envoy.reloadable_features.check_unsupported_typed_per_filter_config")) { | ||
throw EnvoyException( | ||
fmt::format("The filter {} doesn't support virtual host-specific configurations", name)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we ignore the unsupported typed per filter config for the optional http filter also? I assume there will be the same upgrade issue with the new filter. like, the filter added typed per filter config in the new version, the old version can't support it. Although there is a runtime flag here, the is_optional flag feels better.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I think that if is_optional
is set, we should ignore unknown per-route filter configs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
got it, thanks
sorry for the reply late, I will update the PR after the holidays. |
Signed-off-by: He Jie Xu <hejie.xu@intel.com>
Signed-off-by: He Jie Xu <hejie.xu@intel.com>
… optional Signed-off-by: He Jie Xu <hejie.xu@intel.com>
Signed-off-by: He Jie Xu <hejie.xu@intel.com>
Signed-off-by: He Jie Xu <hejie.xu@intel.com>
Signed-off-by: He Jie Xu <hejie.xu@intel.com>
Can you resolve conflicts? Other than that LGTM |
Signed-off-by: He Jie Xu <hejie.xu@intel.com>
Just resolved, thanks! |
Signed-off-by: He Jie Xu <hejie.xu@intel.com>
@lizan thanks! |
Enable `is_optional` field for `HttpFilter`. The default value is `false`, it will keep the same behavior with the current implementation. The envoy will reject the unsupported HTTP filter, also will reject the unsupported HTTP filter in typed per filter config. When the value is `true`, the unsupported HTTP filter will be ignored by the envoy, also will be ignored by typed per filter config, with a warning log. Risk Level: low Testing: unit tests and integration tests are added Docs Changes: API doc is added Release Notes: added as new feature Fixes envoyproxy#15770 Fixes envoyproxy#15025 Signed-off-by: He Jie Xu <hejie.xu@intel.com>
Commit Message: xds: enable the
is_optional
field for HttpFilterAdditional Description:
Enable
is_optional
field forHttpFilter
. The default value isfalse
, it will keep the same behavior with the current implementation. The envoy will reject the unsupported HTTP filter, also will reject the unsupported HTTP filter in typed per filter config. When the value istrue
, the unsupported HTTP filter will be ignored by the envoy, also will be ignored by typed per filter config, with a warning log.Risk Level: low
Testing: unit tests and integration tests are added
Docs Changes: API doc is added
Release Notes: added as new feature
Fixes #15770
Fixes #15025