The Cluster Autoscaler on CAPTF machine pools
Until this week the docs said the Kubernetes Cluster Autoscaler cannot drive a CAPTF machine pool. That was true of one way of running it and wrong about the rest. The Cluster Autoscaler’s clusterapi provider cannot drive a pool. Its aws, azure and oci cloud providers can, because they never go through Cluster API at all: they resize the cloud’s scaling group directly, and a CAPTF pool already knows how to live with a group that something else resizes.
The AWS, Azure and OCI machine pool modules gained one variable in v0.1.1 to make that safe: autoscaler = "external". This post shows why the clusterapi route is closed, how the cloud route works, and how to set it up.