Blog suggestion: Autofission — capacity-aware `MaxScale` for Fission

Hi Fission team!

I've built Autofission, an open-source controller that dynamically calculates and updates MaxScale for explicitly opted-in newdeploy functions based on the Kubernetes cluster's current schedulable capacity.

It addresses a limitation I ran into with a fixed MaxScale: a conservative value becomes an artificial ceiling as nodes are added, while a very large value can allow the HPA to create more Pods than the cluster can schedule. Autofission keeps the limit in sync with CPU and memory requests and available capacity, while Fission's HPA and idle reaper remain in control of scaling.

I'd love to see Autofission featured on the Fission blog. It would also be great if Fission eventually addressed this use case upstream.

Thanks!