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.

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

fix: Correct Karpenter Node Pool Docs #674

Merged
merged 1 commit into from
Aug 29, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
4 changes: 2 additions & 2 deletions docs/layers/accounts/tutorials/manual-configuration.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -675,7 +675,7 @@ stacks/orgs/(namespace)/(tenant)/identity/global-region.yaml and add the arn:

```
import:
- orgs/e98s/gov/iam/_defaults
- orgs/acme/gov/iam/_defaults
- mixins/region/global-region
#...

Expand All @@ -694,7 +694,7 @@ If the auto account id is not known, create an empty list instead:

```
import:
- orgs/e98s/gov/iam/_defaults
- orgs/acme/gov/iam/_defaults
- mixins/region/global-region
#...

Expand Down
4 changes: 2 additions & 2 deletions docs/layers/eks/foundational-platform.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ We first deploy the foundation for the cluster. The `eks/cluster` component depl
including Auth Config mapping. We do not deploy any nodes with the cluster initially. Then once EKS is available, we
connect to the cluster and start deploying resources. First is Karpenter. We deploy the Karpenter chart on a Fargate
node and the IAM service role to allow Karpenter to purchase Spot Instances. Karpenter is the only resources that will
be deployed to Fargate. Then we deploy Karpenter Provisioners using the CRD created by the initial Karpenter component.
be deployed to Fargate. Then we deploy Karpenter Node Pools using the CRD created by the initial Karpenter component.
These provisioners will automatically launch and scale the cluster to meet our demands. Next we deploy `idp-roles` to
manage custom roles for the cluster, and deploy `metrics-server` to provide access to resource metrics.

Expand Down Expand Up @@ -49,7 +49,7 @@ those implementations in follow up topics. For details, see the
EKS Cluster, including IAM role to Kubernetes Auth Config mapping.
- [`eks/karpenter`](/components/library/aws/eks/karpenter/): Installs the Karpenter chart on the EKS cluster and
prepares the environment for provisioners.
- [`eks/karpenter-provisioner`](/components/library/aws/eks/karpenter-node-pool/): Deploys Karpenter Provisioners
- [`eks/karpenter-provisioner`](/components/library/aws/eks/karpenter-node-pool/): Deploys Karpenter Node Pools
using CRDs made available by `eks/karpenter`
- [`iam-service-linked-roles`](/components/library/aws/iam-service-linked-roles/): Provisions
[IAM Service-Linked](https://docs.aws.amazon.com/IAM/latest/UserGuide/using-service-linked-roles.html) roles. These
Expand Down
Loading