I'm developing a Kubernetes native operator focused on service level objectives (SLOs). I believe having a dedicated SLO operator could greatly benefit SREs working with Kubernetes. My question to you all is: what do you think about this operator taking actions when an SLO breach occurs? For instance, I have an example of a ServiceLevelObjective definition that specifies some basic actions, such as scaling a deployment if the availability target is not met. I'd love to hear your thoughts on this idea!
2 Answers
This reminds me of Pyrra. What makes this operator's approach different? I’m curious about your take on that.
What sets this apart from Horizontal Pod Autoscaling (HPA)? It seems like you're implementing similar functions for scaling due to SLO breaches.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures