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

[monitoring-kubernetes] node-exporter: parse containerd config #1866

Merged
merged 10 commits into from Jun 27, 2022

Conversation

yalosev
Copy link
Member

@yalosev yalosev commented Jun 24, 2022

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.

kubelet-eviction-threshold-exporter /bin/loop: line 33: crictl: command not found      

Changelog entries

section: monitoring-kubernetes
type: fix
summary: Make the `kubelet-eviction-threshold-exporter` workable in managed Kubernetes platforms (AWS, GKE, Yandex, etc).

Signed-off-by: Yuriy Losev <yuriy.losev@flant.com>
@yalosev yalosev self-assigned this Jun 24, 2022
@yalosev 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>
Signed-off-by: Yuriy Losev <yuriy.losev@flant.com>
Signed-off-by: Yuriy Losev <yuriy.losev@flant.com>
@yalosev yalosev added the status/backport Backport pr label Jun 24, 2022
@yalosev yalosev added this to the v1.33.9 milestone Jun 24, 2022
@yalosev yalosev marked this pull request as ready for review June 24, 2022 14:42
@yalosev yalosev requested a review from nabokihms as a code owner June 24, 2022 14:42
nabokihms
nabokihms previously approved these changes Jun 25, 2022
Copy link
Member

@nabokihms nabokihms left a 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.

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>
RomanenkoDenys
RomanenkoDenys previously approved these changes Jun 27, 2022
@nabokihms nabokihms added the area/monitoring Pull requests that update monitoring modules label Jun 27, 2022
nabokihms
nabokihms previously approved these changes Jun 27, 2022
Signed-off-by: Yuriy Losev <yuriy.losev@flant.com>
@yalosev yalosev dismissed stale reviews from nabokihms and RomanenkoDenys via e684b6e June 27, 2022 10:17
@nabokihms nabokihms added the e2e/run/yandex-cloud Run e2e tests in Yandex Cloud label Jun 27, 2022
@deckhouse-BOaTswain
Copy link
Collaborator

deckhouse-BOaTswain commented Jun 27, 2022

🟢 e2e: Yandex.Cloud for deckhouse:containerd-exporter succeeded in 31m54s.

Workflow details

🟢 e2e: Yandex.Cloud, Containerd, Kubernetes 1.21 succeeded in 31m18s.

@github-actions github-actions bot removed the e2e/run/yandex-cloud Run e2e tests in Yandex Cloud label Jun 27, 2022
@nabokihms nabokihms merged commit b61984e into main Jun 27, 2022
@nabokihms nabokihms deleted the containerd-exporter branch June 27, 2022 11:32
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)
@z9r5
Copy link
Member

z9r5 commented Jun 27, 2022

Cherry-picked into release-1.33

@z9r5 z9r5 removed the status/backport Backport pr label Jun 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/monitoring Pull requests that update monitoring modules
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants