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

docs: Improve CAS to Karpenter migration steps for clarity and automation #7343

Open
wants to merge 12 commits into
base: main
Choose a base branch
from

Conversation

mozammil89
Copy link

Fixes #N/A

Description

  • Added CloudFormation template to automate setup of IAM role, policy, and interruption queue for EC2 events.
  • Refined security group tagging, separating SG configurations for Launch Templates for better clarity.
  • Simplified Karpenter deployment by passing node affinity settings directly to the Helm chart, eliminating the need for manual CRD installation.
  • Made minor updates to improve overall readability and clarity in the documentation.

How was this change tested?

  • Doc updates tested locally with hugo server
  • Dry-run of steps in an existing EKS cluster with managed node group

Does this change impact docs?

  • Yes, PR includes docs updates
  • Yes, issue opened: #
  • [] No

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@mozammil89 mozammil89 requested a review from a team as a code owner November 7, 2024 04:30
Copy link

netlify bot commented Nov 7, 2024

Deploy Preview for karpenter-docs-prod ready!

Name Link
🔨 Latest commit b5be7d1
🔍 Latest deploy log https://app.netlify.com/sites/karpenter-docs-prod/deploys/6735e9921df6700008a076e6
😎 Deploy Preview https://deploy-preview-7343--karpenter-docs-prod.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

* You will use existing VPC and subnets
* You will use existing security groups
* You will use an existing VPC and subnets
* You will use an existing security groups

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should not have an an because security groups is plural

* Your nodes are part of one or more node groups
* Your workloads have pod disruption budgets that adhere to [EKS best practices](https://aws.github.io/aws-eks-best-practices/karpenter/)
* Your cluster has an [OIDC provider](https://docs.aws.amazon.com/eks/latest/userguide/enable-iam-roles-for-service-accounts.html) for service accounts

This guide will also assume you have the `aws` CLI installed.
This guide will also assume you have the `aws` CLI and Helm client installed.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just helm instead Helm client?

Comment on lines -124 to -126
podAntiAffinity:
requiredDuringSchedulingIgnoredDuringExecution:
- topologyKey: "kubernetes.io/hostname"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe this should stay, why would we remove it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants