Linked content doesn't explain how Karpenter works with CAS

[chrpotr]

The Karpenter FAQs include the following:

How does Karpenter interact with Kubernetes features?

• Kubernetes Cluster Autoscaler: Karpenter can work alongside Cluster Autoscaler. See Kubernetes Cluster Autoscaler for details.

The Kubernetes Cluster Autoscaler link points to this section of the concepts:

Kubernetes Cluster Autoscaler Like Karpenter, Kubernetes Cluster Autoscaler is designed to add nodes when requests come in to run pods that cannot be met by current capacity. Cluster autoscaler is part of the Kubernetes project, with implementations by most major Kubernetes cloud providers. By taking a fresh look at provisioning, Karpenter offers the following improvements:

• Designed to handle the full flexibility of the cloud: Karpenter has the ability to efficiently address the full range of instance types available through AWS. Cluster autoscaler was not originally built with the flexibility to handle hundreds of instance types, zones, and purchase options.
• Quick node provisioning: Karpenter manages each instance directly, without use of additional orchestration mechanisms like node groups. This enables it to retry in milliseconds instead of minutes when capacity is unavailable. It also allows Karpenter to leverage diverse instance types, availability zones, and purchase options without the creation of hundreds of node groups.

The linked content doesn't really explain how Karpenter works with CAS.

[jonathan-innis]

It's a good callout. I'd love to see how we can improve our documentation around CAS/Karpenter or to expand out the existing migration guide: https://karpenter.sh/docs/getting-started/migrating-from-cas/. @chrpotr Is this something that you'd be interested in helping out on or finding someone to help out on?