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.

Sign up for GitHub

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 Provisioner Docs Example #1231

Merged
merged 3 commits into from
Feb 1, 2022
Merged

Update Provisioner Docs Example #1231

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
2d4b847
Update Provisioner Docs Example
DWSR Jan 27, 2022
581a360
Update preview docs instead
DWSR Feb 1, 2022
c7f79a8
Update website/content/en/preview/provisioner.md
ellistarn Feb 1, 2022
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
4 changes: 2 additions & 2 deletions website/content/en/preview/provisioner.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,7 @@ spec:
# Limits prevent Karpenter from creating new instances once the limit is exceeded.
limits:
resources:
cpu: 1000
cpu: "1000"
memory: 1000Gi

# These fields vary per cloud provider, see your cloud provider specific documentation
Expand Down Expand Up @@ -162,7 +162,7 @@ The provisioner spec includes a limits section (`spec.limits.resources`), which

Presently, Karpenter supports `memory` and `cpu` limits.

CPU limits are described with a `DecimalSI` value, usually a natural integer.
CPU limits are described with a `DecimalSI` value. Note that the Kubernetes API will coerce this into a string, so we recommend against using integers to avoid GitOps skew.

Memory limits are described with a [`BinarySI` value, such as 1000Gi.](https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#meaning-of-memory)

Expand Down