Installing Karpenter on an Existing EKS Cluster

#aws #kubernetes #awstutorial
⏰ Timecodes ⏰
00:00 Install Karpenter
10:13 Review the Karpenter details
11:51 Create & Scale out the cluster
13:41 Scale in the deployment & Node termination

[@Hdiwinsndbhejhdbb]

Very nice guidance

[@FastTrackTechEd]

Thank you...

[@VivekMishra-wp5zh]

Excellent video

[@FastTrackTechEd]

Thanks

[@VivekMishra-wp5zh]

@@FastTrackTechEd can you also make video of cleaning up

[@Ronaldoroot]

Very good

[@FastTrackTechEd]

Thanks

[@Ronaldoroot]

I wonder why the new node was created with an ec2 c7a.medium and not t3.medium?

[@10serendipity]

Detailed video. Thank you! Can it be installed using provisioner instead of nodepool or is it deprecated?

[@FastTrackTechEd]

Yes it deprecated, better to use provisioner

[@muvvalabharath3845]

@@FastTrackTechEd for what version of karpenter helm_release we can use provisoner. I installed karpenter helm_chart version 0.36.2. No provisoner CRD is created

[@surajthakur7796]

How did the new node created in existing node group even though you updated karpenter.yaml node affinity to point to node group name ?

[@FastTrackTechEd]

By design the Karpenter pods are running within the managed node group, but the nodes created by Karpenter are not running in any node group.

[@muvvalabharath3845]

I'm using karpenter but I'm getting some downtime for my services during consolidation of nodes. Is there anyway to get 0 downtime for pods managed by karpenter

[@FastTrackTechEd]

You can use "topologySpreadConstraints" if your application has multiple pods.

[@netturtech3410]

Malayaaliiiiiiii ?