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

enable networkCost for KubeCost #66

Open
csantanapr opened this issue Jun 29, 2023 · 0 comments
Open

enable networkCost for KubeCost #66

csantanapr opened this issue Jun 29, 2023 · 0 comments

Comments

@csantanapr
Copy link
Member

csantanapr commented Jun 29, 2023

When installing kubecost with the following command

eksdemo install kubecost-eks-amp -c "$CLUSTER_NAME" --node-exporter --ingress-host "kubecost.$ROUTE53_HOSTED_ZONE" --ingress-class=nginx --nginx-pass "$PASSWORD" --dry-run

It doesn't enable networkCost by default.
I think it would be useful to enable networkCost configured with AWS settings as described in the docs
https://docs.kubecost.com/install-and-configure/advanced-configuration/network-costs-configuration#enabling-network-costs

What it takes is to pass some extra values to the helm install, this will configure and install the deamonset/agent

Network cost, which is disabled by default, needs to be run as a privileged pod to access the relevant networking kernel module on the host machine.

Not sure if the privileged pod in would work on fargate or boottlerocket out of the box

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