GeistHaus
log in · sign up

Disruption

karpenter.sh

Understand different ways Karpenter disrupts nodes

3 pages link to this URL
Under the hood: Amazon EKS ultra scale clusters | Amazon Web Services

This post was co-authored by Shyam Jeedigunta, Principal Engineer, Amazon EKS; Apoorva Kulkarni, Sr. Specialist Solutions Architect, Containers and Raghav Tripathi, Sr. Software Dev Manager, Amazon EKS. Today, Amazon Elastic Kubernetes Service (Amazon EKS) announced support for clusters with up to 100,000 nodes. With Amazon EC2’s new generation accelerated computing instance types, this translates to […]

1 inbound link article en Amazon Elastic Kubernetes Service Amazon Elastic Kubernetes ServiceAnnouncementsArtificial IntelligenceAWS TrainiumBest PracticesOpen SourceAmazon EKSAmazon Elastic Kubernetes Service (Amazon EKS)artificial intelligencecomputeKarpenterKubernetesopen source
Amazon EKS-Optimized Amazon Linux 2023 AMIs Now Available | Amazon Web Services

Introduction We are excited to announce general availability of Amazon Linux 2023 (AL2023) on Amazon Elastic Kubernetes Service (Amazon EKS). AL2023 is the next generation of Amazon Linux from Amazon Web Services (AWS) and is designed to provide a secure, stable, high-performance environment to develop and run your cloud applications. The standard AL2023-based EKS-optimized Amazon […]

1 inbound link article en Amazon Elastic Kubernetes Service Amazon Elastic Kubernetes ServiceAnnouncementsAmazon EKSContainers
kubernetes finalizers

I was reading the Disruption section of the Karpenter docs and the first sentence says, Karpenter sets a Kubernetes finalizer on each node and node claim it...

0 inbound links article en