Hey SCL,
The Cluster API (CAPI) project is looking for people to contribute to its MachinePool functionality. This has been discussed in the CAPI office hours a number of times but sending this to the list to widen the audience.
The core CAPI maintainers have done a fantastic job trying to keep MachinePools moving forward, but there is only so much time they have. What the project needs is people looking at this specific feature to take it where it needs to be and give it some love.
MachinePools have been experimental in CAPI for a very long time. The graduation from experimental to GA isn't an option at present, as there are a number of issues and missing features that need to be resolved before graduation can be considered.
The feature is fundamental to the implementation of managed Kubernetes (EKS, AKS, GKE) support in providers like CAPA, CAPZ and CAPG. The longer MachinePools aren't actively maintained, the more they will fall behind the rest of CAPI.
A few of us (4 so far) have expressed an interest and will be getting together every week Tuesday 8am PT to discuss, plan and try to move things forward.
If you are interested in helping out, please reach out here or in #cluster-api.....any help will be greatly appreciated.
Rich