We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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
The text was updated successfully, but these errors were encountered:
No branches or pull requests
When installing kubecost with the following command
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
Not sure if the privileged pod in would work on fargate or boottlerocket out of the box
The text was updated successfully, but these errors were encountered: