We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug Kubelet logs are not forwarded if systemd is not enabled
Logs
sumologic-kubernetes-collection/deploy/helm/sumologic/conf/logs/otelcol/config.yaml
Line 386 in 7c1008b
To Reproduce Set value to false here
sumologic-kubernetes-collection/deploy/helm/sumologic/values.yaml
Line 348 in 7c1008b
Expected behavior Kubelet logs should be controlled by a kubelet.enabled key instead of a systemd.enabled key.
Environment (please complete the following information):
Anything else do we need to know I have a fork which includes the new kubelet.enabled to control forwarding of kubelet logs. Draft PR: #3168
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug
Kubelet logs are not forwarded if systemd is not enabled
Logs
sumologic-kubernetes-collection/deploy/helm/sumologic/conf/logs/otelcol/config.yaml
Line 386 in 7c1008b
To Reproduce
Set value to false here
sumologic-kubernetes-collection/deploy/helm/sumologic/values.yaml
Line 348 in 7c1008b
Expected behavior
Kubelet logs should be controlled by a kubelet.enabled key instead of a systemd.enabled key.
Environment (please complete the following information):
Chart version = 3.10.0
Anything else do we need to know
I have a fork which includes the new kubelet.enabled to control forwarding of kubelet logs. Draft PR: #3168
The text was updated successfully, but these errors were encountered: