Closed michaelmdresser closed 9 months ago
Remove content type header for /prediction/speccost calls
Backend no longer requires it, makes us flexible for yaml and json
Added JSON manifest support to kubectl cost predict
kubectl cost predict
Tested the server-side change in https://github.com/kubecost/kubecost-cost-model/pull/1916 with kubectl-cost and predictions with an input YAML file are unaffected.
kubectl-cost
What does this PR change?
Remove content type header for /prediction/speccost calls
Backend no longer requires it, makes us flexible for yaml and json
Does this PR rely on any other PRs?
How does this PR impact users? (This is the kind of thing that goes in release notes!)
Added JSON manifest support to
kubectl cost predict
How was this PR tested?
Have you made an update to documentation?