spin-operator
spin-operator copied to clipboard
Consider implementing scale sub-resource on `SpinApp` so that HPA/KEDA can point directly at `SpinApp`
This would allow the spin operator to handle the scaling of the underlying deployment and would obviate the need for enableAutoscaling field.
Is #86 potentially relevant here?
Is #86 potentially relevant here?
Yep, one more reason to want to support /scale. IMO still not urgent though.
While I still don't think this is super urgent I'm kind of spinning my wheels looking for something to build so I'm going to assign myself here and take a crack at this issue.
Fixed: https://github.com/spinkube/spin-operator/pull/268