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.
Signed-off-by: Arnaldo Garcia Rincon agarrcia@amazon.com
Issue number:
N / A
Description of changes:
In b696d6f, the new
kubernetes.log-level
setting was implemented but in the actual model the name of the new setting waskubelet_log_level
. This renames it tolog_level
since that's what is used in the templated configuration files and in the documentation.If I attempt to set the log level, the drop-in file for the kubelet isn't updated:
-v <level>
is missing which should be after--register-with-taints
as shown here.Testing done:
I started an
aws-k8s-1.22
instance and run the following commands while tailing the journal logs:I didn't see any errors and I confirmed the setting was used, whereas with the previous configuration this setting wasn't rendered:
Terms of contribution:
By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.