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

Renamed constraints doc to provisioning and fixed links #947

Merged
merged 1 commit into from
Dec 8, 2021
Merged

Renamed constraints doc to provisioning and fixed links #947

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
0 website/content/en/docs/AWS/constraints.md → website/content/en/docs/AWS/provisioning.md
View file
Open in desktop
File renamed without changes.
2 changes: 1 addition & 1 deletion website/content/en/docs/provisioner-crd.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -141,7 +141,7 @@ Karpenter supports specifying capacity type, which is analogous to [EC2 purchase

This section is cloud provider specific. Reference the appropriate documentation:

- [AWS](../aws/constraints/)
chrisnegus marked this conversation as resolved.
Show resolved Hide resolved
- [AWS](../aws/provisioning/)



2 changes: 1 addition & 1 deletion website/content/en/docs/tasks/provisioning-task.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ If you want to modify or add provisioners to Karpenter, do the following:

* [Provisioner](../../getting-started/#provisioner) in the Getting Started guide for a sample default Provisioner
* [Provisioner API](../../provisioner-crd) for descriptions of Provisioner API values
* [Provisioning Configuration](../../AWS/constraints) for cloud-specific settings
* [Provisioning Configuration](../../AWS/provisioning) for cloud-specific settings

2. Apply the new or modified Provisioner to the cluster.

Expand Down
2 changes: 1 addition & 1 deletion website/content/en/docs/tasks/running-pods.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -60,7 +60,7 @@ Its limits are set to 256MiB of memory and 1 CPU.
Instance type selection math only uses `requests`, but `limits` may be configured to enable resource oversubscription.


See [Managing Resources for Containers](https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/) for details on resource types supported by Kubernetes, [Specify a memory request and a memory limit](https://kubernetes.io/docs/tasks/configure-pod-container/assign-memory-resource/#specify-a-memory-request-and-a-memory-limit) for examples of memory requests, and [Provisioning Configuration](../../aws/constraints) for a list of supported resources.
See [Managing Resources for Containers](https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/) for details on resource types supported by Kubernetes, [Specify a memory request and a memory limit](https://kubernetes.io/docs/tasks/configure-pod-container/assign-memory-resource/#specify-a-memory-request-and-a-memory-limit) for examples of memory requests, and [Provisioning Configuration](../../aws/provisioning/) for a list of supported resources.


## Selecting nodes (`nodeSelector` and `nodeAffinity`)
Expand Down