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

Update spec-cost-prediction-api.md #822

Merged
merged 2 commits into from
Dec 14, 2023
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions apis/apis-overview/spec-cost-prediction-api.md
Original file line number Diff line number Diff line change
Expand Up @@ -66,6 +66,8 @@ Set to `true` to ignore historical usage data (if it exists) when making the pre

The API requires that workloads be passed in the request body in YAML format and that the `Content-Type` header be set to `application/yaml`. Multiple workloads can be passed via separation with the standard `---` syntax.

The API requires that workloads be passed in the request body in YAML or JSON format. If using YAML, multiple workloads can be passed via separation with the standard `---` syntax. If using JSON, multiple workloads can be passed via the standard "list" format used by Kubernetes (e.g. `kubectl get deployment -A -o json`).

michaelmdresser marked this conversation as resolved.
Show resolved Hide resolved
Currently supported workload types:

* Deployments
Expand Down