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

Allow to control the log chattiness of the Kubelet #3

Open
corvus-ch opened this issue Dec 11, 2020 · 2 comments
Open

Allow to control the log chattiness of the Kubelet #3

corvus-ch opened this issue Dec 11, 2020 · 2 comments
Labels
enhancement New feature or request

Comments

@corvus-ch
Copy link
Contributor

Context

By default, the log level of the Kubelet is set to debug. This generates a lot of noise in the logs. It also results in a huge amount of data stored within logging (Elastisearch). The log level should be configurable through the configuration hierarchy. Section "3. Persistent configuration for OCP 4.6 and later" in https://access.redhat.com/solutions/4619431 explains how this can be done.

@corvus-ch corvus-ch added the enhancement New feature or request label Dec 11, 2020
@corvus-ch corvus-ch changed the title Allow to controll the chattiness of kubleg logs Allow to controll the log chattiness of the Kubelet Dec 11, 2020
@tobru tobru changed the title Allow to controll the log chattiness of the Kubelet Allow to control the log chattiness of the Kubelet Dec 11, 2020
@tobru
Copy link
Member

tobru commented Dec 11, 2020

This issue might belong into https://github.com/appuio/component-openshift4-nodes/issues?

@corvus-ch
Copy link
Contributor Author

corvus-ch commented Dec 14, 2020

This issue might belong into https://github.com/appuio/component-openshift4-nodes/issues?

The issue asks for creating a MachineConfig. Doing so is not restricted to the openshift4-nodes component but can be done in any component. As a matter of facts, this component already does so (https://github.com/appuio/component-openshift4-logging/blob/b88b0c6/component/main.jsonnet#L51). So this issue is filed with the correct component.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants