You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As the OCI Helm chart is signed by [Cosign](https://github.com/sigstore/cosign) as part of the release process you can verify the chart before installing it by running the following command.
Copy file name to clipboardExpand all lines: website/content/en/docs/concepts/scheduling.md
+6-1Lines changed: 6 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -159,8 +159,11 @@ Take care to ensure the label domains are correct. A well known label like `karp
159
159
| kubernetes.io/os | linux | Operating systems are defined by [GOOS values](https://github.com/golang/go/blob/master/src/internal/syslist/syslist.go) (`KnownOS`) on the instance |
160
160
| kubernetes.io/arch | amd64 | Architectures are defined by [GOARCH values](https://github.com/golang/go/blob/master/src/internal/syslist/syslist.go) (`KnownArch`) on the instance |
161
161
| karpenter.sh/capacity-type | spot | Capacity types include `reserved`, `spot`, and `on-demand` |
162
+
| karpenter.sh/nodepool | default | The name of the nodepool used to provision the node. |
162
163
| karpenter.k8s.aws/capacity-reservation-id | cr-56fac701cc1951b03 | [AWS Specific] The capacity reservation ID. Only present on reserved nodes. |
163
164
| karpenter.k8s.aws/capacity-reservation-type | default | [AWS Specific] The capacity reservation type. Can be `default` or `capacity-block`. Only present on reserved nodes. |
165
+
| karpenter.k8s.aws/capacity-reservation-interruptible | true | [AWS Specific] Whether the capacity reservation is interruptible. Only present on reserved nodes. |
166
+
| karpenter.k8s.aws/ec2nodeclass | default | [AWS Specific] The name of the ec2 nodeclass used to provision the node |
164
167
| karpenter.k8s.aws/instance-hypervisor | nitro | [AWS Specific] Instance types that use a specific hypervisor |
165
168
| karpenter.k8s.aws/instance-encryption-in-transit-supported | true | [AWS Specific] Instance types that support (or not) in-transit encryption |
166
169
| karpenter.k8s.aws/instance-category | g | [AWS Specific] Instance types of the same category, usually the string before the generation number |
@@ -180,7 +183,9 @@ Take care to ensure the label domains are correct. A well known label like `karp
180
183
| karpenter.k8s.aws/instance-gpu-memory | 16384 | [AWS Specific] Number of mebibytes of memory on the GPU |
181
184
| karpenter.k8s.aws/instance-local-nvme | 900 | [AWS Specific] Number of gibibytes of local nvme storage on the instance |
Karpenter translates the following deprecated labels to their stable equivalents: `failure-domain.beta.kubernetes.io/zone`, `failure-domain.beta.kubernetes.io/region`, `beta.kubernetes.io/arch`, `beta.kubernetes.io/os`, and `beta.kubernetes.io/instance-type`.
Copy file name to clipboardExpand all lines: website/content/en/docs/contributing/documentation-updates.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,4 +9,4 @@ description: >
9
9
- Documentation for https://karpenter.sh/docs/ is built under website/content/en/preview/.
10
10
- Documentation updates should be made to the "preview" directory. Your changes will be promoted to website/content/en/docs/ by an automated process after the change has been merged.
11
11
- Previews for your changes are built and available a few minutes after you push. Look for the "Amplify Preview URL" link in a comment in your PR.
12
-
- If your update applies to more than just the current version of Karpenter, please backport your changes into all of the versions under website/content/en/
12
+
- If your update applies to more than just the current version of Karpenter, please backport your changes into all of the versions under website/content/en/*besides* the /docs/ folder
Copy file name to clipboardExpand all lines: website/content/en/docs/faq.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ See [Configuring NodePools]({{< ref "./concepts/#configuring-nodepools" >}}) for
17
17
AWS is the first cloud provider supported by Karpenter, although it is designed to be used with other cloud providers as well.
18
18
19
19
### Can I write my own cloud provider for Karpenter?
20
-
Yes, but there is no documentation yet for it. Start with Karpenter's GitHub [cloudprovider](https://github.com/aws/karpenter-provider-aws/tree/v1.9.0/pkg/cloudprovider) documentation to see how the AWS provider is built, but there are other sections of the code that will require changes too.
20
+
Yes, but there is no documentation yet for it. Start with Karpenter's GitHub [cloudprovider](https://github.com/aws/karpenter-provider-aws/tree/v1.10.0/pkg/cloudprovider) documentation to see how the AWS provider is built, but there are other sections of the code that will require changes too.
21
21
22
22
### What operating system nodes does Karpenter deploy?
23
23
Karpenter uses the OS defined by the [AMI Family in your EC2NodeClass]({{< ref "./concepts/nodeclasses#specamifamily" >}}).
@@ -29,7 +29,7 @@ Karpenter has multiple mechanisms for configuring the [operating system]({{< ref
29
29
Karpenter is flexible to multi-architecture configurations using [well known labels]({{< ref "./concepts/scheduling/#supported-labels">}}).
30
30
31
31
### What RBAC access is required?
32
-
All the required RBAC rules can be found in the Helm chart template. See [clusterrole-core.yaml](https://github.com/aws/karpenter/blob/v1.9.0/charts/karpenter/templates/clusterrole-core.yaml), [clusterrole.yaml](https://github.com/aws/karpenter/blob/v1.9.0/charts/karpenter/templates/clusterrole.yaml), [rolebinding.yaml](https://github.com/aws/karpenter/blob/v1.9.0/charts/karpenter/templates/rolebinding.yaml), and [role.yaml](https://github.com/aws/karpenter/blob/v1.9.0/charts/karpenter/templates/role.yaml) files for details.
32
+
All the required RBAC rules can be found in the Helm chart template. See [clusterrole-core.yaml](https://github.com/aws/karpenter/blob/v1.10.0/charts/karpenter/templates/clusterrole-core.yaml), [clusterrole.yaml](https://github.com/aws/karpenter/blob/v1.10.0/charts/karpenter/templates/clusterrole.yaml), [rolebinding.yaml](https://github.com/aws/karpenter/blob/v1.10.0/charts/karpenter/templates/rolebinding.yaml), and [role.yaml](https://github.com/aws/karpenter/blob/v1.10.0/charts/karpenter/templates/role.yaml) files for details.
33
33
34
34
### Can I run Karpenter outside of a Kubernetes cluster?
35
35
Yes, as long as the controller has network and IAM/RBAC access to the Kubernetes API and your provider API.
Copy file name to clipboardExpand all lines: website/content/en/docs/getting-started/getting-started-with-karpenter/_index.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,7 +48,7 @@ After setting up the tools, set the Karpenter and Kubernetes version:
48
48
49
49
```bash
50
50
export KARPENTER_NAMESPACE="kube-system"
51
-
export KARPENTER_VERSION="1.9.0"
51
+
export KARPENTER_VERSION="1.10.0"
52
52
export K8S_VERSION="1.34"
53
53
```
54
54
@@ -115,13 +115,13 @@ See [Enabling Windows support](https://docs.aws.amazon.com/eks/latest/userguide/
115
115
As the OCI Helm chart is signed by [Cosign](https://github.com/sigstore/cosign) as part of the release process you can verify the chart before installing it by running the following command.
0 commit comments