Feature: Implement /scale subresource to allow resource autoscaling

[tomkerkhove]

KEDA is an application autoscaler for KEDA which allows you to autoscale anything, as long as it supports /scale subresource.

If Azure Service Operator would support it, we could automatically scale Azure SQL DBs, VMs and more based on Azure Monitor metrics.

[tomkerkhove]

Any thoughts on this @matthchr ?

[tomkerkhove]

Bump

[matthchr]

@tomkerkhove - Agree that this would be cool, at least for a small subset of resources where it makes sense (there are lots where it doesn't).

We're currently focusing on some efforts related to code generation (see #1192) which will involve a number of new (generated) resources being added to ASO. It's unlikely that this will be done by us prior that. We'll pick up other items after that work depending on overall interest.

[tomkerkhove]

Thanks for letting me know!

What's the estimate for this? Just to know.

[tomkerkhove]

Any thoughts/updates on this @matthchr?

[matthchr]

Not much different than above. We've got an alpha out for ASOv2 (based on code generation) today, but there's still a good amount of work to be done there before it's at a place of beta quality. From our perspective this is an interesting but lower priority ask. We'll hopefully get around to it, but probably not for a while yet.

[tomkerkhove]

Now that it has hit GA, I'm wondering if this is planned? Would be major!

[tomkerkhove]

Any thoughts @theunrepentantgeek ?

[denniszielke]

Would really like to have the capability to scale up VMSS via CRD by using Keda. This would help us a lot compute heavy workloads that need to be scaled up and down by external metrics.

[matthchr]

We still think this is interesting but haven't had a chance to figure out exactly what it would look like generically across resources.

[tomkerkhove]

Let me know if you are interested!

[matthchr]

We definitely are still interested in this. I also recently spoke with @palma21 about this as well. Currently we're pretty focused on bringing ASO to GA with the feature set that it has now. Once that's done we can look into tackling this. It's definitely an interesting ask and would be a differentiator for us, so it's likely to get done we just need to get the time to do it.

[tomkerkhove]

That's lovely to hear! Let me know when I can help with something.

[tomkerkhove]

Any update on this?

[matthchr]

Not yet @tomkerkhove - our plan is the same as mentioned in Oct, GA first and then will investigate this. GA is slated for the next release (which will be 2.0.0), hopefully will happen sometime first half of Feb, after which we should have more cycles to look at this.

[tomkerkhove]

Thanks for the update!

[theunrepentantgeek]

We should do the research for this to work out what's involved - moving into v2.2.0 for this.

[tomkerkhove]

Any ETA for this feature?

[theunrepentantgeek]

Top candidate to pull into v2.8.0 if we have time.

[tomkerkhove]

Let me know if you want to sync up in terms of KEDA integration!