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

Jump to bottom

docs: Make the latest K8s version to a parameter #4918

Merged
merged 1 commit into from
Oct 24, 2023
Merged

docs: Make the latest K8s version to a parameter #4918

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.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
1 change: 1 addition & 0 deletions website/config.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -67,6 +67,7 @@ params:
icon: fab fa-slack
desc: 'Chat with us on Slack in the #aws-provider channel'
latest_release_version: v0.31.1
latest_k8s_version: 1.28
versions:
- v0.31
- v0.30
Expand Down
6 changes: 3 additions & 3 deletions website/content/en/preview/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -176,10 +176,10 @@ Yes, see the [KubeletConfiguration Section in the NodePool docs]({{<ref "./conce
The difference between the Core and Full variants is that Core is a minimal OS with less components and no graphic user interface (GUI) or desktop experience.
`Windows2019` and `Windows2022` AMI families use the Windows Server Core option for simplicity, but if required, you can specify a custom AMI to run Windows Server Full.

You can specify the [Amazon EKS optimized AMI](https://docs.aws.amazon.com/eks/latest/userguide/eks-optimized-windows-ami.html) with Windows Server 2022 Full for Kubernetes 1.28 by configuring an `amiSelector` that references the AMI name.
```
You can specify the [Amazon EKS optimized AMI](https://docs.aws.amazon.com/eks/latest/userguide/eks-optimized-windows-ami.html) with Windows Server 2022 Full for Kubernetes {{< param "latest_k8s_version" >}} by configuring an `amiSelector` that references the AMI name.
```yaml
amiSelectorTerms:
- name: Windows_Server-2022-English-Full-EKS_Optimized-1.28*
- name: Windows_Server-2022-English-Full-EKS_Optimized-{{< param "latest_k8s_version" >}}*
jonathan-innis marked this conversation as resolved.
Show resolved Hide resolved
```

## Deprovisioning
Expand Down
5 changes: 3 additions & 2 deletions ...ite/content/en/preview/getting-started/getting-started-with-karpenter/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,10 +41,11 @@ authenticate properly by running `aws sts get-caller-identity`.

### 2. Set environment variables

After setting up the tools, set the Karpenter version number:
After setting up the tools, set the Karpenter and Kubernetes version:

```bash
export KARPENTER_VERSION={{< param "latest_release_version" >}}
export K8S_VERSION={{< param "latest_k8s_version" >}}
```

Then set the following environment variable:
Expand All @@ -56,7 +57,7 @@ If you open a new shell to run steps in this procedure, you need to set some or
To remind yourself of these values, type:

```bash
echo $KARPENTER_VERSION $CLUSTER_NAME $AWS_DEFAULT_REGION $AWS_ACCOUNT_ID $TEMPOUT
echo $KARPENTER_VERSION $K8S_VERSION $CLUSTER_NAME $AWS_DEFAULT_REGION $AWS_ACCOUNT_ID $TEMPOUT
```

{{% /alert %}}
Expand Down
2 changes: 1 addition & 1 deletion ...n/preview/getting-started/getting-started-with-karpenter/scripts/step02-create-cluster.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ kind: ClusterConfig
metadata:
name: ${CLUSTER_NAME}
region: ${AWS_DEFAULT_REGION}
version: "1.28"
version: "${K8S_VERSION}"
tags:
karpenter.sh/discovery: ${CLUSTER_NAME}

Expand Down