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

Scrape metrics from kubernetes nodes and container runtime #33

Closed
arturo-seijas opened this issue Aug 23, 2022 · 2 comments
Closed

Scrape metrics from kubernetes nodes and container runtime #33

arturo-seijas opened this issue Aug 23, 2022 · 2 comments

Comments

@arturo-seijas
Copy link

Enhancement Proposal

Given the COS is a kubernetes bundle, it think I'd be a really nice addition to discover and scrape all the kubernetes components without the need of manual configuration and also nodes and pods, although the latter would probably require another charm to be deployed along the current charms in the bundle.

Also, adding grafana dashboards for these metrics could come in handy too.

Thank you!

@simskij simskij changed the title Scrape metrics from kubernetes nodes and container runtime runtime Scrape metrics from kubernetes nodes and container runtime Aug 24, 2022
@simskij
Copy link
Member

simskij commented Aug 24, 2022

I agree with you. We've previously discussed this and it is really a two-part proposal.

  1. We need to be able to collect telemetry for CK8s. This is likely to be solved using the planned grafana-agent machine charm, which among other things include node_exporter.
  2. We need to be able to collect telemetry for MicroK8s. This is likely to be solved using a proxy charm and a telemetry plugin that will deploy node_exporter, kubestate-metrics`, and the kubernetes metrics server.

What we don't want to do is to open the flood gate that is kubernetes_sd_config as that would invite less ideal usage models that don't leverage everything that the juju topology has to offer.

@simskij
Copy link
Member

simskij commented Apr 5, 2023

This will be addressed by the K8s team. Closing this issue as it is a no-op on our side.

@simskij simskij closed this as completed Apr 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants