Skip to content

Commit c60f577

Browse files
authored
Docs: updates for 1.3.2 release (#7870)
1 parent c88c5b5 commit c60f577

File tree

15 files changed

+40
-40
lines changed

15 files changed

+40
-40
lines changed

charts/karpenter-crd/Chart.yaml

+2-2
Original file line numberDiff line numberDiff line change
@@ -2,8 +2,8 @@ apiVersion: v2
22
name: karpenter-crd
33
description: A Helm chart for Karpenter Custom Resource Definitions (CRDs).
44
type: application
5-
version: 1.3.1
6-
appVersion: 1.3.1
5+
version: 1.3.2
6+
appVersion: 1.3.2
77
keywords:
88
- cluster
99
- node

charts/karpenter/Chart.yaml

+2-2
Original file line numberDiff line numberDiff line change
@@ -2,8 +2,8 @@ apiVersion: v2
22
name: karpenter
33
description: A Helm chart for Karpenter, an open-source node provisioning project built for Kubernetes.
44
type: application
5-
version: 1.3.1
6-
appVersion: 1.3.1
5+
version: 1.3.2
6+
appVersion: 1.3.2
77
keywords:
88
- cluster
99
- node

charts/karpenter/README.md

+6-6
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
A Helm chart for Karpenter, an open-source node provisioning project built for Kubernetes.
44

5-
![Version: 1.3.1](https://img.shields.io/badge/Version-1.3.1-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 1.3.1](https://img.shields.io/badge/AppVersion-1.3.1-informational?style=flat-square)
5+
![Version: 1.3.2](https://img.shields.io/badge/Version-1.3.2-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 1.3.2](https://img.shields.io/badge/AppVersion-1.3.2-informational?style=flat-square)
66

77
## Documentation
88

@@ -15,7 +15,7 @@ You can follow the detailed installation instruction in the [documentation](http
1515
```bash
1616
helm upgrade --install --namespace karpenter --create-namespace \
1717
karpenter oci://public.ecr.aws/karpenter/karpenter \
18-
--version 1.3.1 \
18+
--version 1.3.2 \
1919
--set "serviceAccount.annotations.eks\.amazonaws\.com/role-arn=${KARPENTER_IAM_ROLE_ARN}" \
2020
--set settings.clusterName=${CLUSTER_NAME} \
2121
--set settings.interruptionQueue=${CLUSTER_NAME} \
@@ -27,13 +27,13 @@ helm upgrade --install --namespace karpenter --create-namespace \
2727
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.
2828

2929
```shell
30-
cosign verify public.ecr.aws/karpenter/karpenter:1.3.1 \
30+
cosign verify public.ecr.aws/karpenter/karpenter:1.3.2 \
3131
--certificate-oidc-issuer=https://token.actions.githubusercontent.com \
3232
--certificate-identity-regexp='https://github\.com/aws/karpenter-provider-aws/\.github/workflows/release\.yaml@.+' \
3333
--certificate-github-workflow-repository=aws/karpenter-provider-aws \
3434
--certificate-github-workflow-name=Release \
35-
--certificate-github-workflow-ref=refs/tags/v1.3.1 \
36-
--annotations version=1.3.1
35+
--certificate-github-workflow-ref=refs/tags/v1.3.2 \
36+
--annotations version=1.3.2
3737
```
3838

3939
## Values
@@ -51,7 +51,7 @@ cosign verify public.ecr.aws/karpenter/karpenter:1.3.1 \
5151
| controller.healthProbe.port | int | `8081` | The container port to use for http health probe. |
5252
| controller.image.digest | string | `"sha256:3fffcbbb6d0b1a2183a07bbe52c902d344fa41f8a8485de43760432ef7e2fd17"` | SHA256 digest of the controller image. |
5353
| controller.image.repository | string | `"public.ecr.aws/karpenter/controller"` | Repository path to the controller image. |
54-
| controller.image.tag | string | `"1.3.1"` | Tag of the controller image. |
54+
| controller.image.tag | string | `"1.3.2"` | Tag of the controller image. |
5555
| controller.metrics.port | int | `8080` | The container port to use for metrics. |
5656
| controller.resources | object | `{}` | Resources for the controller pod. |
5757
| controller.sidecarContainer | list | `[]` | Additional sidecarContainer config |

charts/karpenter/values.yaml

+1-1
Original file line numberDiff line numberDiff line change
@@ -108,7 +108,7 @@ controller:
108108
# -- Repository path to the controller image.
109109
repository: public.ecr.aws/karpenter/controller
110110
# -- Tag of the controller image.
111-
tag: 1.3.1
111+
tag: 1.3.2
112112
# -- SHA256 digest of the controller image.
113113
digest: sha256:3fffcbbb6d0b1a2183a07bbe52c902d344fa41f8a8485de43760432ef7e2fd17
114114
# -- Additional environment variables for the controller pod.

website/content/en/docs/faq.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ See [Configuring NodePools]({{< ref "./concepts/#configuring-nodepools" >}}) for
1717
AWS is the first cloud provider supported by Karpenter, although it is designed to be used with other cloud providers as well.
1818

1919
### 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-core/tree/v1.3.1/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-core/tree/v1.3.2/pkg/cloudprovider) documentation to see how the AWS provider is built, but there are other sections of the code that will require changes too.
2121

2222
### What operating system nodes does Karpenter deploy?
2323
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
2929
Karpenter is flexible to multi-architecture configurations using [well known labels]({{< ref "./concepts/scheduling/#supported-labels">}}).
3030

3131
### 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.3.1/charts/karpenter/templates/clusterrole-core.yaml), [clusterrole.yaml](https://github.com/aws/karpenter/blob/v1.3.1/charts/karpenter/templates/clusterrole.yaml), [rolebinding.yaml](https://github.com/aws/karpenter/blob/v1.3.1/charts/karpenter/templates/rolebinding.yaml), and [role.yaml](https://github.com/aws/karpenter/blob/v1.3.1/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.3.2/charts/karpenter/templates/clusterrole-core.yaml), [clusterrole.yaml](https://github.com/aws/karpenter/blob/v1.3.2/charts/karpenter/templates/clusterrole.yaml), [rolebinding.yaml](https://github.com/aws/karpenter/blob/v1.3.2/charts/karpenter/templates/rolebinding.yaml), and [role.yaml](https://github.com/aws/karpenter/blob/v1.3.2/charts/karpenter/templates/role.yaml) files for details.
3333

3434
### Can I run Karpenter outside of a Kubernetes cluster?
3535
Yes, as long as the controller has network and IAM/RBAC access to the Kubernetes API and your provider API.

website/content/en/docs/getting-started/getting-started-with-karpenter/_index.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ After setting up the tools, set the Karpenter and Kubernetes version:
4848

4949
```bash
5050
export KARPENTER_NAMESPACE="kube-system"
51-
export KARPENTER_VERSION="1.3.1"
51+
export KARPENTER_VERSION="1.3.2"
5252
export K8S_VERSION="1.32"
5353
```
5454

@@ -115,13 +115,13 @@ See [Enabling Windows support](https://docs.aws.amazon.com/eks/latest/userguide/
115115
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.
116116

117117
```bash
118-
cosign verify public.ecr.aws/karpenter/karpenter:1.3.1 \
118+
cosign verify public.ecr.aws/karpenter/karpenter:1.3.2 \
119119
--certificate-oidc-issuer=https://token.actions.githubusercontent.com \
120120
--certificate-identity-regexp='https://github\.com/aws/karpenter-provider-aws/\.github/workflows/release\.yaml@.+' \
121121
--certificate-github-workflow-repository=aws/karpenter-provider-aws \
122122
--certificate-github-workflow-name=Release \
123-
--certificate-github-workflow-ref=refs/tags/v1.3.1 \
124-
--annotations version=1.3.1
123+
--certificate-github-workflow-ref=refs/tags/v1.3.2 \
124+
--annotations version=1.3.2
125125
```
126126

127127
{{% alert title="DNS Policy Notice" color="warning" %}}

website/content/en/docs/getting-started/migrating-from-cas/_index.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -92,7 +92,7 @@ One for your Karpenter node role and one for your existing node group.
9292
First set the Karpenter release you want to deploy.
9393
9494
```bash
95-
export KARPENTER_VERSION="1.3.1"
95+
export KARPENTER_VERSION="1.3.2"
9696
```
9797

9898
We can now generate a full Karpenter deployment yaml from the Helm chart.
@@ -132,7 +132,7 @@ Now that our deployment is ready we can create the karpenter namespace, create t
132132
133133
## Create default NodePool
134134
135-
We need to create a default NodePool so Karpenter knows what types of nodes we want for unscheduled workloads. You can refer to some of the [example NodePool](https://github.com/aws/karpenter/tree/v1.3.1/examples/v1) for specific needs.
135+
We need to create a default NodePool so Karpenter knows what types of nodes we want for unscheduled workloads. You can refer to some of the [example NodePool](https://github.com/aws/karpenter/tree/v1.3.2/examples/v1) for specific needs.
136136
137137
{{% script file="./content/en/{VERSION}/getting-started/migrating-from-cas/scripts/step10-create-nodepool.sh" language="bash" %}}
138138

website/content/en/docs/reference/cloudformation.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ These descriptions should allow you to understand:
1717
To download a particular version of `cloudformation.yaml`, set the version and use `curl` to pull the file to your local system:
1818

1919
```bash
20-
export KARPENTER_VERSION="1.3.1"
20+
export KARPENTER_VERSION="1.3.2"
2121
curl https://raw.githubusercontent.com/aws/karpenter-provider-aws/v"${KARPENTER_VERSION}"/website/content/en/preview/getting-started/getting-started-with-karpenter/cloudformation.yaml > cloudformation.yaml
2222
```
2323

website/content/en/docs/reference/threat-model.md

+5-5
Original file line numberDiff line numberDiff line change
@@ -31,11 +31,11 @@ A Cluster Developer has the ability to create pods via `Deployments`, `ReplicaSe
3131

3232
Karpenter has permissions to create and manage cloud instances. Karpenter has Kubernetes API permissions to create, update, and remove nodes, as well as evict pods. For a full list of the permissions, see the RBAC rules in the helm chart template. Karpenter also has AWS IAM permissions to create instances with IAM roles.
3333

34-
* [aggregate-clusterrole.yaml](https://github.com/aws/karpenter/blob/v1.3.1/charts/karpenter/templates/aggregate-clusterrole.yaml)
35-
* [clusterrole-core.yaml](https://github.com/aws/karpenter/blob/v1.3.1/charts/karpenter/templates/clusterrole-core.yaml)
36-
* [clusterrole.yaml](https://github.com/aws/karpenter/blob/v1.3.1/charts/karpenter/templates/clusterrole.yaml)
37-
* [rolebinding.yaml](https://github.com/aws/karpenter/blob/v1.3.1/charts/karpenter/templates/rolebinding.yaml)
38-
* [role.yaml](https://github.com/aws/karpenter/blob/v1.3.1/charts/karpenter/templates/role.yaml)
34+
* [aggregate-clusterrole.yaml](https://github.com/aws/karpenter/blob/v1.3.2/charts/karpenter/templates/aggregate-clusterrole.yaml)
35+
* [clusterrole-core.yaml](https://github.com/aws/karpenter/blob/v1.3.2/charts/karpenter/templates/clusterrole-core.yaml)
36+
* [clusterrole.yaml](https://github.com/aws/karpenter/blob/v1.3.2/charts/karpenter/templates/clusterrole.yaml)
37+
* [rolebinding.yaml](https://github.com/aws/karpenter/blob/v1.3.2/charts/karpenter/templates/rolebinding.yaml)
38+
* [role.yaml](https://github.com/aws/karpenter/blob/v1.3.2/charts/karpenter/templates/role.yaml)
3939

4040
## Assumptions
4141

website/content/en/v1.3/faq.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ See [Configuring NodePools]({{< ref "./concepts/#configuring-nodepools" >}}) for
1717
AWS is the first cloud provider supported by Karpenter, although it is designed to be used with other cloud providers as well.
1818

1919
### 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-core/tree/v1.3.1/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-core/tree/v1.3.2/pkg/cloudprovider) documentation to see how the AWS provider is built, but there are other sections of the code that will require changes too.
2121

2222
### What operating system nodes does Karpenter deploy?
2323
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
2929
Karpenter is flexible to multi-architecture configurations using [well known labels]({{< ref "./concepts/scheduling/#supported-labels">}}).
3030

3131
### 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.3.1/charts/karpenter/templates/clusterrole-core.yaml), [clusterrole.yaml](https://github.com/aws/karpenter/blob/v1.3.1/charts/karpenter/templates/clusterrole.yaml), [rolebinding.yaml](https://github.com/aws/karpenter/blob/v1.3.1/charts/karpenter/templates/rolebinding.yaml), and [role.yaml](https://github.com/aws/karpenter/blob/v1.3.1/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.3.2/charts/karpenter/templates/clusterrole-core.yaml), [clusterrole.yaml](https://github.com/aws/karpenter/blob/v1.3.2/charts/karpenter/templates/clusterrole.yaml), [rolebinding.yaml](https://github.com/aws/karpenter/blob/v1.3.2/charts/karpenter/templates/rolebinding.yaml), and [role.yaml](https://github.com/aws/karpenter/blob/v1.3.2/charts/karpenter/templates/role.yaml) files for details.
3333

3434
### Can I run Karpenter outside of a Kubernetes cluster?
3535
Yes, as long as the controller has network and IAM/RBAC access to the Kubernetes API and your provider API.

website/content/en/v1.3/getting-started/getting-started-with-karpenter/_index.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ After setting up the tools, set the Karpenter and Kubernetes version:
4848

4949
```bash
5050
export KARPENTER_NAMESPACE="kube-system"
51-
export KARPENTER_VERSION="1.3.1"
51+
export KARPENTER_VERSION="1.3.2"
5252
export K8S_VERSION="1.32"
5353
```
5454

@@ -115,13 +115,13 @@ See [Enabling Windows support](https://docs.aws.amazon.com/eks/latest/userguide/
115115
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.
116116

117117
```bash
118-
cosign verify public.ecr.aws/karpenter/karpenter:1.3.1 \
118+
cosign verify public.ecr.aws/karpenter/karpenter:1.3.2 \
119119
--certificate-oidc-issuer=https://token.actions.githubusercontent.com \
120120
--certificate-identity-regexp='https://github\.com/aws/karpenter-provider-aws/\.github/workflows/release\.yaml@.+' \
121121
--certificate-github-workflow-repository=aws/karpenter-provider-aws \
122122
--certificate-github-workflow-name=Release \
123-
--certificate-github-workflow-ref=refs/tags/v1.3.1 \
124-
--annotations version=1.3.1
123+
--certificate-github-workflow-ref=refs/tags/v1.3.2 \
124+
--annotations version=1.3.2
125125
```
126126

127127
{{% alert title="DNS Policy Notice" color="warning" %}}

website/content/en/v1.3/getting-started/migrating-from-cas/_index.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -92,7 +92,7 @@ One for your Karpenter node role and one for your existing node group.
9292
First set the Karpenter release you want to deploy.
9393
9494
```bash
95-
export KARPENTER_VERSION="1.3.1"
95+
export KARPENTER_VERSION="1.3.2"
9696
```
9797

9898
We can now generate a full Karpenter deployment yaml from the Helm chart.
@@ -132,7 +132,7 @@ Now that our deployment is ready we can create the karpenter namespace, create t
132132
133133
## Create default NodePool
134134
135-
We need to create a default NodePool so Karpenter knows what types of nodes we want for unscheduled workloads. You can refer to some of the [example NodePool](https://github.com/aws/karpenter/tree/v1.3.1/examples/v1) for specific needs.
135+
We need to create a default NodePool so Karpenter knows what types of nodes we want for unscheduled workloads. You can refer to some of the [example NodePool](https://github.com/aws/karpenter/tree/v1.3.2/examples/v1) for specific needs.
136136
137137
{{% script file="./content/en/{VERSION}/getting-started/migrating-from-cas/scripts/step10-create-nodepool.sh" language="bash" %}}
138138

website/content/en/v1.3/reference/cloudformation.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ These descriptions should allow you to understand:
1717
To download a particular version of `cloudformation.yaml`, set the version and use `curl` to pull the file to your local system:
1818

1919
```bash
20-
export KARPENTER_VERSION="1.3.1"
20+
export KARPENTER_VERSION="1.3.2"
2121
curl https://raw.githubusercontent.com/aws/karpenter-provider-aws/v"${KARPENTER_VERSION}"/website/content/en/preview/getting-started/getting-started-with-karpenter/cloudformation.yaml > cloudformation.yaml
2222
```
2323

website/content/en/v1.3/reference/threat-model.md

+5-5
Original file line numberDiff line numberDiff line change
@@ -31,11 +31,11 @@ A Cluster Developer has the ability to create pods via `Deployments`, `ReplicaSe
3131

3232
Karpenter has permissions to create and manage cloud instances. Karpenter has Kubernetes API permissions to create, update, and remove nodes, as well as evict pods. For a full list of the permissions, see the RBAC rules in the helm chart template. Karpenter also has AWS IAM permissions to create instances with IAM roles.
3333

34-
* [aggregate-clusterrole.yaml](https://github.com/aws/karpenter/blob/v1.3.1/charts/karpenter/templates/aggregate-clusterrole.yaml)
35-
* [clusterrole-core.yaml](https://github.com/aws/karpenter/blob/v1.3.1/charts/karpenter/templates/clusterrole-core.yaml)
36-
* [clusterrole.yaml](https://github.com/aws/karpenter/blob/v1.3.1/charts/karpenter/templates/clusterrole.yaml)
37-
* [rolebinding.yaml](https://github.com/aws/karpenter/blob/v1.3.1/charts/karpenter/templates/rolebinding.yaml)
38-
* [role.yaml](https://github.com/aws/karpenter/blob/v1.3.1/charts/karpenter/templates/role.yaml)
34+
* [aggregate-clusterrole.yaml](https://github.com/aws/karpenter/blob/v1.3.2/charts/karpenter/templates/aggregate-clusterrole.yaml)
35+
* [clusterrole-core.yaml](https://github.com/aws/karpenter/blob/v1.3.2/charts/karpenter/templates/clusterrole-core.yaml)
36+
* [clusterrole.yaml](https://github.com/aws/karpenter/blob/v1.3.2/charts/karpenter/templates/clusterrole.yaml)
37+
* [rolebinding.yaml](https://github.com/aws/karpenter/blob/v1.3.2/charts/karpenter/templates/rolebinding.yaml)
38+
* [role.yaml](https://github.com/aws/karpenter/blob/v1.3.2/charts/karpenter/templates/role.yaml)
3939

4040
## Assumptions
4141

website/hugo.yaml

+1-1
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,7 @@ params:
7676
url: "https://slack.k8s.io/"
7777
icon: fab fa-slack
7878
desc: "Chat with us on Slack in the #aws-provider channel"
79-
latest_release_version: "1.3.1"
79+
latest_release_version: "1.3.2"
8080
latest_k8s_version: "1.32"
8181
versions:
8282
- v1.3

0 commit comments

Comments
 (0)