Releases: kubecost/kubectl-cost
Releases · kubecost/kubectl-cost
v0.6.6
v0.6.5
v0.6.4
v0.6.3
Add --opencost flag for targeting Opencost as the service for the cost command by @vladComan0 in #173.
Full Changelog: v0.6.2...v0.6.3
v0.6.2: Patch CVEs
What's Changed
- Fixed OpenCost URL by @mattray in #165
- Patch CVEs by upgrading golang.org/x/net and github.com/emicklei/go-restful by @michaelmdresser in #168
Full Changelog: v0.6.1...v0.6.2
v0.6.1
What's Changed
- Fix predict integration tests by removing old flag by @michaelmdresser in #157
- Remove content type header for /prediction/speccost API calls by @michaelmdresser in #161
- Add parameter
idle(default true) which togglesincludeIdleandidlequery params to Allocation API by @michaelmdresser in #164
Full Changelog: v0.6.0...v0.6.1
v0.6.0
- #145:
kubectl cost predictSplits window flag into two separate flags. One for determining historical usage, and another for determining costs. This allows users to use reconciled cost data by passing a 48hr offset window. - #146: Added
--show-totaland--hide-diffflags tokubectl cost predict. "Total" cost is the expected monthly cost of each workload if the new spec were applied to your cluster. "Diff" cost (the default) is the expected monthly cost change of applying each new spec to your cluster. - #148: Fix kubectl-cost crashing on systems without glibc by disabling CGO for all builds
v0.5.0
- #143 Changed
kubectl cost predictto use Kubecost's new/prediction/speccostAPI released in Kubecost v1.101. This supports more accurate cost diffing including usage data if available. - #144 Pivoted the
kubectl cost predictoutput format to reduce width while also increasing available data. Try it out!
v0.4.1
v0.4.0
#141:
- Added basic cost diffing support to
kubectl cost predict. The default behavior will attempt to match workload specs with existing workloads tracked by Kubecost and will calculate a cost diff based on resource request. Disable with--no-diff. - Added a namespace to the
kubectl cost predictworkload name output. If a namespace is not set on a given workload, it will be inherited from your Kubeconfig context.