Releases: kubecost/kubectl-cost
Releases · kubecost/kubectl-cost
v0.3.1
v0.3.0
- Introduced
kubectl cost predict
, a tool to estimate the monthly cost of a workload's requests based on real resource costs as determined by Kubecost. Requires a v1.100+ Kubecost backend. Try it withkubectl cost predict -f my-deployment.yaml
, or seepredict --help
and the README! - Introduced the
--release-name
(-r
) to simplify using Kubecost backends deployed in namespaces other thankubecost
#131
v0.2.13
v0.2.12
v0.2.11
v0.2.10: Kubectl cost to support ENV variable to use proxy
#122 - adding environment variable KUBECTL_COST_USE_PROXY to also provide way to use proxy along with --use-proxy flag. Before this change there's was no way to set use-proxy with environment variables
v0.2.9: OpenCost support! (and more)
- #115:
kubectl cost
will only port-forward to Pods in a Ready state. Previously,kubectl cost
could fail with a panic if the first cost-analyzer pod listed by the equivalent ofkubectl get pods
was in a non-Ready state (like Error or Completed). - #117: Adds support for OpenCost by introducing the new flags
--allocation-path
and--service-port
. Check out--help
for some tips on how to use them with OpenCost! If you're running OpenCost inside the Kubecost Helm chart, all you need iskubectl cost --allocation-path "/model/allocation/compute"
! - #118: The log level is now configurable with
--log-level
(e.g.kubectl cost --log-level debug
). Try it out!
v0.2.8
- From the community: #109. Short names for common resources:
ns
,po
,no
,deploy
. Thanks @kranurag7!
v0.2.7
v0.2.6
Bump for CI fix.