Ritika

Hi, @JorTurFer , I'd like to take this up. What I understood is we have to remove `rolloutStartegy` from : - apis/keda/v1alpha1/scaledjob_types.go - controllers/keda/scaledjob_controller.go - config/crd/bases/keda.sh_scaledjobs.yaml There is no mention...

> Thanks! Unfortunately we cannot do this yet as this is a breaking change and we have to wait for KEDA 3.X. oh! alright! seems like a rational approach !...

Hi @JoelSpeed , the same issue is faced in OpenShift with volumesnapshot provided by CSI and virtualservices provided by ServiceMesh. This PR is extremely useful. Are we waiting for further...

> But if others are willing to continue the discussion then I welcome that. Else I'll try and find some time to get to this soon @JoelSpeed thanks for the...

Hi @JoelSpeed Is this PR still in progress or it is on hold for now? Looking forward for this change.

> On the other hand kubectl get logs scanner-db-7484ff5c96-dsgg9 init-db does work and print the logs correclty. I suppose you mean `kubectl logs scanner-db-7484ff5c96-dsgg9 init-db` can you send the log...

Do you mean you can't replicate the issue? the issue is already open @Ithrael

It happened to me as well. I am able to replicate this issue.

I checked and the error is there. It is not present in the code as well , it can be an upcoming feature/enhancement. It is supposed to be like `autoscale`...

I think this is an error if there is no discussion of making it a command . WDYT /sig cli