hpvd

+1 on this, was also thinking about using KEDA when, talking about the relationship between size and spinup duration / faster dynamic scaling in the advantages of distroless topic https://github.com/streamnative/function-mesh/issues/448

regarding KEDA: this is a good introduction: https://medium.com/backstagewitharchitects/how-autoscaling-works-in-kubernetes-why-you-need-to-start-using-keda-b601b483d355 (the embedded video is also interesting)

there is already a blogpost saying that KEDA may be a future direction (at the end of https://streamnative.cn/blog/engineering/2022-01-19-auto-scaling-pulsar-functions-in-kubernetes-using-custom-metrics-zh/)

of course in some/many usecases the possibility to easily autoscale to zero would help a lot in the field of infrastructure costs...

@tpiperatgod thanks for your question. We are still incubating our new company ;-) It's in the field of mechanical engineering... We are looking into pulsar for streaming but also for...

thanks for your warm words. Yes, there was a lot of great progress and there are many good things on the way... e.g. - this issue about scaling using Keda...

these 2 points may be interesting for testing and release of this new functionality: # 1) new in latest KEDA (v2.8): Activation and Scaling Thresholds Previously in KEDA, when scaling...

if already an independent debug image is needed, one may take the chance to look into to - stripdown the main image further to completely `distroless` and - go/propose for...

Following link provided above, today in v0.4: **10 vulnerabilities** have been detected in this package's images. 

in link above to redhat, the redhat security score of A unfortunately has no real meaningfulness for the total security: > **This image includes layers and packages that cannot be...