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

Deploy only network cost DS into shoot cluster #7

Open
phyrog opened this issue Oct 10, 2024 · 0 comments
Open

Deploy only network cost DS into shoot cluster #7

phyrog opened this issue Oct 10, 2024 · 0 comments

Comments

@phyrog
Copy link
Member

phyrog commented Oct 10, 2024

At the moment, all KubeCost components are deployed into the shoot cluster (including its own Prometheus).

This can be improved by leveraging the Prometheus and Plutono deployed in the seed cluster. Since the cost-analyzer needs query access to Prometheus, it makes sense to deploy the cost-analyzer into the seed cluster too. I believe the only component that needs to run in the shoot cluster is the network cost daemonset, as this will analyze the traffic going in and out of pods on the shoot nodes.

A few things that need investigating:

  • are all the necessary metrics collected from node-exporter and cadvisor?
  • do all metrics have the necessary labels?
  • how can the kubecost manifests be split across seed/shoot while still make them easily updatable?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant