Markus Thömmes
Markus Thömmes
To clarify additionally: `targetBurstCapacity` behaves correct here. It's only making sure that the activators are in path. What's not behaving as expected is the activator's routing and loadbalancing behavior.
I'll append as well. Multi-tenant use-case here too and indeed troublesome.
I tend to disagree with this being a black and white decision. If Knative Serving was installed without the operator, changes should definitely be made through ConfigMap edits. If Knative...
If you're using an operator, the surface area of what you can do should be encoded by the operator. If we encourage users to reach around we imo have failed...
Done. I was staging PRs and didn't notice the other one actually merged.
Hmm. Gotta fix the code generation. Will take care of that.
Hmm. This diff is becoming much larger than intended because the PodSpec grew quiet a bit between versions, I suppose.
@benjaminhuo As mentioned above, this diff has grown quite a bit. We could try to make it smaller by upgrading controller-runtime in smaller steps or trying to break the K8s...
This is a known limitation of the custom/external metrics API. A possible solution is to come up with an aggregation API as per https://github.com/kubernetes-incubator/custom-metrics-apiserver/issues/3. Knative's HPA support suffers from the...
Looking at your comments in #24985 I think I agree that `recoverWith` should be "brought back". The changes you propose make sense. Am I reading them correctly that that would...