Tanvi,
Are you talking about autoscaling the selenium nodes (or) are you talking about autoscaling the selenium standalone instances ?
When it comes to the selenium nodes, I believe the scaling needs to happen based on the new session queue and so the Grid Hub should make the decision on whether it needs to add more nodes or not.
If you are using Selenium Grid 3, you can consider the following:
https://github.com/aerokube/ggr (You can also explore the Go Grid Router, which kind of places the role of a load balancer so that you can distribute load across multiple grids. I dont know if it supports auto scaling though)
and lastly you can take a look at
https://github.com/RationaleEmotions/just-ask that kind of works on an auto scaling mode. But this implementation is confined to being locked with a single docker host. It doesn't need any container orchestration tool. It spins off containers on-demand and then works with them.
Grid 4 is the way forward. So you should definitely consider exploring Grid 4 because it bakes in a lot of the needs for distributed testing into it itself and thus making all other wrapper solutions redundant.
Thanks & Regards
Krishnan Mahadevan
"All the desirable things in life are either illegal, expensive, fattening or in love with someone else!"
My Scribblings @ http://wakened-cognition.blogspot.com/