-
Notifications
You must be signed in to change notification settings - Fork 5.3k
Closed
Labels
triageIssue requires triageIssue requires triage
Description
Title: What's the correct way to disable extensions?
Description:
Following this documentation https://www.envoyproxy.io/docs/envoy/v1.15.0/operations/cli.html?highlight=disable%20extensions#cmdoption-disable-extensions, I tried to start envoy with
envoy -c <myconfig> --disable-extensions grpc_credentials/envoy.grpc_credentials.file_based_metadata
However, I see this error message in the console
[2020-11-19 01:44:34.216][1][warning][misc] failed to disable unknown extension 'grpc_credentials/envoy.grpc_credentials.file_based_metadata'
Following the logs on startup I can see this
I1119 01:44:34.216 1 envoy] [1][main][source/server/server.cc:297] statically linked extensions:
I1119 01:44:34.216 1 envoy] [1][main][source/server/server.cc:299] envoy.grpc_credentials: envoy.grpc_credentials.aws_iam, envoy.grpc_credentials.default, envoy.grpc_credentials.file_based_metadata
I am using envoy version v1.15.0
What's the correct way to define the list of extensions to disable?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
triageIssue requires triageIssue requires triage