Skip to content

Commit

Permalink
docs: remove eksctl note and bump min version
Browse files Browse the repository at this point in the history
  • Loading branch information
jmdeal committed May 30, 2024
1 parent b8e235c commit 646c293
Show file tree
Hide file tree
Showing 6 changed files with 3 additions and 63 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ Install these tools before proceeding:

1. [AWS CLI](https://docs.aws.amazon.com/cli/latest/userguide/install-cliv2-linux.html)
2. `kubectl` - [the Kubernetes CLI](https://kubernetes.io/docs/tasks/tools/install-kubectl-linux/)
3. `eksctl` (>= v0.179.0) - [the CLI for AWS EKS](https://docs.aws.amazon.com/eks/latest/userguide/eksctl.html)
3. `eksctl` (>= v0.180.0) - [the CLI for AWS EKS](https://docs.aws.amazon.com/eks/latest/userguide/eksctl.html)
4. `helm` - [the package manager for Kubernetes](https://helm.sh/docs/intro/install/)

[Configure the AWS CLI](https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-quickstart.html)
Expand Down Expand Up @@ -89,16 +89,6 @@ The following cluster configuration will:

{{% script file="./content/en/{VERSION}/getting-started/getting-started-with-karpenter/scripts/step06-add-spot-role.sh" language="bash"%}}

{{% alert title="EKSCTL Breaking Change" color="warning" %}}
Starting with `eksctl` v1.77.0, a service account is created for each podIdentityAssociation.
This default service account is incompatible with the Karpenter Helm chart, and it will need to be removed to proceed with installation.
If you're on an affected version of `eksctl` and you created a cluster with a `podIdentityAssociation`, run the following command before proceeding with the rest of the installation.
This has been identified as a breaking change in `eksctl` which will be addressed in a future release ([GitHub Issue](https://github.com/eksctl-io/eksctl/issues/7775)).
```bash
kubectl delete sa -n ${KARPENTER_NAMESPACE} karpenter
```
{{% /alert %}}

{{% alert title="Windows Support Notice" color="warning" %}}
In order to run Windows workloads, Windows support should be enabled in your EKS Cluster.
See [Enabling Windows support](https://docs.aws.amazon.com/eks/latest/userguide/windows-support.html#enable-windows-support) to learn more.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ Install these tools before proceeding:

1. [AWS CLI](https://docs.aws.amazon.com/cli/latest/userguide/install-cliv2-linux.html)
2. `kubectl` - [the Kubernetes CLI](https://kubernetes.io/docs/tasks/tools/install-kubectl-linux/)
3. `eksctl` (>= v0.179.0) - [the CLI for AWS EKS](https://docs.aws.amazon.com/eks/latest/userguide/eksctl.html)
3. `eksctl` (>= v0.180.0) - [the CLI for AWS EKS](https://docs.aws.amazon.com/eks/latest/userguide/eksctl.html)
4. `helm` - [the package manager for Kubernetes](https://helm.sh/docs/intro/install/)

[Configure the AWS CLI](https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-quickstart.html)
Expand Down Expand Up @@ -89,16 +89,6 @@ The following cluster configuration will:

{{% script file="./content/en/{VERSION}/getting-started/getting-started-with-karpenter/scripts/step06-add-spot-role.sh" language="bash"%}}

{{% alert title="EKSCTL Breaking Change" color="warning" %}}
Starting with `eksctl` v1.77.0, a service account is created for each podIdentityAssociation.
This default service account is incompatible with the Karpenter Helm chart, and it will need to be removed to proceed with installation.
If you're on an affected version of `eksctl` and you created a cluster with a `podIdentityAssociation`, run the following command before proceeding with the rest of the installation.
This has been identified as a breaking change in `eksctl` which will be addressed in a future release ([GitHub Issue](https://github.com/eksctl-io/eksctl/issues/7775)).
```bash
kubectl delete sa -n ${KARPENTER_NAMESPACE} karpenter
```
{{% /alert %}}

{{% alert title="Windows Support Notice" color="warning" %}}
In order to run Windows workloads, Windows support should be enabled in your EKS Cluster.
See [Enabling Windows support](https://docs.aws.amazon.com/eks/latest/userguide/windows-support.html#enable-windows-support) to learn more.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -81,16 +81,6 @@ The following cluster configuration will:

{{% script file="./content/en/{VERSION}/getting-started/getting-started-with-karpenter/scripts/step06-add-spot-role.sh" language="bash"%}}

{{% alert title="EKSCTL Breaking Change" color="warning" %}}
Starting with `eksctl` v1.77.0, a service account is created for each podIdentityAssociation.
This default service account is incompatible with the Karpenter Helm chart, and it will need to be removed to proceed with installation.
If you're on an affected version of `eksctl` and you created a cluster with a `podIdentityAssociation`, run the following command before proceeding with the rest of the installation.
This has been identified as a breaking change in `eksctl` which will be addressed in a future release ([GitHub Issue](https://github.com/eksctl-io/eksctl/issues/7775)).
```bash
kubectl delete sa -n ${KARPENTER_NAMESPACE} karpenter
```
{{% /alert %}}

{{% alert title="Windows Support Notice" color="warning" %}}
In order to run Windows workloads, Windows support should be enabled in your EKS Cluster.
See [Enabling Windows support](https://docs.aws.amazon.com/eks/latest/userguide/windows-support.html#enable-windows-support) to learn more.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -89,16 +89,6 @@ The following cluster configuration will:

{{% script file="./content/en/{VERSION}/getting-started/getting-started-with-karpenter/scripts/step06-add-spot-role.sh" language="bash"%}}

{{% alert title="EKSCTL Breaking Change" color="warning" %}}
Starting with `eksctl` v1.77.0, a service account is created for each podIdentityAssociation.
This default service account is incompatible with the Karpenter Helm chart, and it will need to be removed to proceed with installation.
If you're on an affected version of `eksctl` and you created a cluster with a `podIdentityAssociation`, run the following command before proceeding with the rest of the installation.
This has been identified as a breaking change in `eksctl` which will be addressed in a future release ([GitHub Issue](https://github.com/eksctl-io/eksctl/issues/7775)).
```bash
kubectl delete sa -n ${KARPENTER_NAMESPACE} karpenter
```
{{% /alert %}}

{{% alert title="Windows Support Notice" color="warning" %}}
In order to run Windows workloads, Windows support should be enabled in your EKS Cluster.
See [Enabling Windows support](https://docs.aws.amazon.com/eks/latest/userguide/windows-support.html#enable-windows-support) to learn more.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -89,16 +89,6 @@ The following cluster configuration will:

{{% script file="./content/en/{VERSION}/getting-started/getting-started-with-karpenter/scripts/step06-add-spot-role.sh" language="bash"%}}

{{% alert title="EKSCTL Breaking Change" color="warning" %}}
Starting with `eksctl` v1.77.0, a service account is created for each podIdentityAssociation.
This default service account is incompatible with the Karpenter Helm chart, and it will need to be removed to proceed with installation.
If you're on an affected version of `eksctl` and you created a cluster with a `podIdentityAssociation`, run the following command before proceeding with the rest of the installation.
This has been identified as a breaking change in `eksctl` which will be addressed in a future release ([GitHub Issue](https://github.com/eksctl-io/eksctl/issues/7775)).
```bash
kubectl delete sa -n ${KARPENTER_NAMESPACE} karpenter
```
{{% /alert %}}

{{% alert title="Windows Support Notice" color="warning" %}}
In order to run Windows workloads, Windows support should be enabled in your EKS Cluster.
See [Enabling Windows support](https://docs.aws.amazon.com/eks/latest/userguide/windows-support.html#enable-windows-support) to learn more.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ Install these tools before proceeding:

1. [AWS CLI](https://docs.aws.amazon.com/cli/latest/userguide/install-cliv2-linux.html)
2. `kubectl` - [the Kubernetes CLI](https://kubernetes.io/docs/tasks/tools/install-kubectl-linux/)
3. `eksctl` (>= v0.179.0) - [the CLI for AWS EKS](https://docs.aws.amazon.com/eks/latest/userguide/eksctl.html)
3. `eksctl` (>= v0.180.0) - [the CLI for AWS EKS](https://docs.aws.amazon.com/eks/latest/userguide/eksctl.html)
4. `helm` - [the package manager for Kubernetes](https://helm.sh/docs/intro/install/)

[Configure the AWS CLI](https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-quickstart.html)
Expand Down Expand Up @@ -89,16 +89,6 @@ The following cluster configuration will:

{{% script file="./content/en/{VERSION}/getting-started/getting-started-with-karpenter/scripts/step06-add-spot-role.sh" language="bash"%}}

{{% alert title="EKSCTL Breaking Change" color="warning" %}}
Starting with `eksctl` v1.77.0, a service account is created for each podIdentityAssociation.
This default service account is incompatible with the Karpenter Helm chart, and it will need to be removed to proceed with installation.
If you're on an affected version of `eksctl` and you created a cluster with a `podIdentityAssociation`, run the following command before proceeding with the rest of the installation.
This has been identified as a breaking change in `eksctl` which will be addressed in a future release ([GitHub Issue](https://github.com/eksctl-io/eksctl/issues/7775)).
```bash
kubectl delete sa -n ${KARPENTER_NAMESPACE} karpenter
```
{{% /alert %}}

{{% alert title="Windows Support Notice" color="warning" %}}
In order to run Windows workloads, Windows support should be enabled in your EKS Cluster.
See [Enabling Windows support](https://docs.aws.amazon.com/eks/latest/userguide/windows-support.html#enable-windows-support) to learn more.
Expand Down

0 comments on commit 646c293

Please sign in to comment.