Backport of fix: log level present in extra args using envoy-extra-args annotation : NET-2190 into release/1.1.x #150
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport
This PR is auto-generated from #133 to be assessed for backporting due to the inclusion of the label backport/1.1.
The below text is copied from the body of the original PR.
PR fixes - hashicorp/consul-k8s#1846
Short description of Issue - The consul.hashicorp.com/envoy-extra-args annotation is not compatible with Consul DataPlane. When we pass extra
loglevel
in consul.hashicorp.com/envoy-extra-args pod shows that the consul-dataplane container already has log-level explicitly set to INFO and service errors out.Solution -
Discussed and agreed upon solution is to override the log level in case extra args also has log level given.
Tested this PR by creating a docker image for consul dataplane, pushing it hub and using the image in this tutorial
I have tested by using my image in tutorial -
imageConsulDataplane: "absolutelightning/consul-dataplane:latest"
Here are the tests results -
Logs of consul data plane -
Overview of commits