Yury Akudovich
Yury Akudovich
Would it be possible to call custom shell script or similar for now to send alerts? Using commercial mailing services wouldn't make sense if there is existing email server.
I've updated the branch with changes from main and locally those e2e test passed: Test logs ``` $ go test -v -tags e2e ./internals/scaling_modifiers/... ./internals/value_metric_type/... === RUN TestScalingModifiers scaling_modifiers_test.go:269: --...
> Could you also update the ChangeLog.md? Added.
Are there any chance to merge this? https://github.com/kedacore/keda/issues/5570 blocks migration to Keda for us in production.
> Any blockers which prevent this to be merged? I don't see any, but there was some discussion in https://github.com/kedacore/keda/issues/5570
Unfortunately only `kubectl version` respects `-v=9`. Here is output of all the commands: ```console $ time kubectl version -v=9 I0119 14:18:55.658263 3484916 loader.go:373] Config loaded from file: /home/yorik/.kube/config I0119 14:18:55.658919...
`--client` doesn't help, it's still very slow: ```console $ time kubectl version --client -v=9 [14:47:22] WARNING: This version information is deprecated and will be replaced with the output from kubectl...
To be honest, I don't care about speed of `kubectl version`, but there is no reason for `kubectl completion` and `kubectl config current-context` to do server request. I can't say...
Running without the config helps: ``` $ time KUBECONFIG=/dev/null kubectl version WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short. Use --output=yaml|json...