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
[monitoring-kubernetes] node-exporter: parse containerd config #1866
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Yuriy Losev <yuriy.losev@flant.com>
yalosev
changed the title
parse containerd config
[monitoring-kubernetes] node-exporter: parse containerd config
Jun 24, 2022
Signed-off-by: Yuriy Losev <yuriy.losev@flant.com>
Signed-off-by: Yuriy Losev <yuriy.losev@flant.com>
Signed-off-by: Yuriy Losev <yuriy.losev@flant.com>
nabokihms
previously approved these changes
Jun 25, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd like Denys to also have a look on this PR, yet it lgtm.
modules/340-monitoring-kubernetes/images/kubelet-eviction-thresholds-exporter/loop
Outdated
Show resolved
Hide resolved
yalosev
force-pushed
the
containerd-exporter
branch
from
June 27, 2022 09:48
4876e5a
to
1c3588b
Compare
yalosev
force-pushed
the
containerd-exporter
branch
from
June 27, 2022 09:49
1c3588b
to
747ecf6
Compare
RomanenkoDenys
requested changes
Jun 27, 2022
modules/340-monitoring-kubernetes/images/kubelet-eviction-thresholds-exporter/loop
Outdated
Show resolved
Hide resolved
Signed-off-by: Yuriy Losev <yuriy.losev@flant.com>
Signed-off-by: Yuriy Losev <yuriy.losev@flant.com>
RomanenkoDenys
previously approved these changes
Jun 27, 2022
nabokihms
previously approved these changes
Jun 27, 2022
Signed-off-by: Yuriy Losev <yuriy.losev@flant.com>
nabokihms
approved these changes
Jun 27, 2022
🟢 Workflow details🟢 |
github-actions
bot
removed
the
e2e/run/yandex-cloud
Run e2e tests in Yandex Cloud
label
Jun 27, 2022
Merged
z9r5
pushed a commit
that referenced
this pull request
Jun 27, 2022
Signed-off-by: Yuriy Losev <yuriy.losev@flant.com> (cherry picked from commit b61984e)
Cherry-picked into release-1.33 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: Yuriy Losev yuriy.losev@flant.com
Description
Managed clusters (EKS, Yandex, GKE) with deckhouse as module couldn't work with kubelet-eviction-threshold-exporter because they don't have crictl and also socket can have different passes. But all of them have /etc/containerd/config.toml, so we can parse it and extract root direction
Why do we need it, and what problem does it solve?
kubelet-eviction-threshold-exporter doesn't work in platform managed kubernetes.
Changelog entries