keda-olm-operator
keda-olm-operator copied to clipboard
kedacore
Operator for deploying KEDA Controller on OperatorHub.io/OLM
### Use-Case https://github.com/kedacore/keda-olm-operator/blob/main/RELEASE-PROCESS.md
This isn't a feature request but neither is an actual bug report, at least not with the operator itself. Currently observing that Openshift instances on IBM Cloud and on AWS...
### Use-Case https://github.com/kedacore/keda-olm-operator/blob/main/RELEASE-PROCESS.md ### Specification - [ ] https://github.com/kedacore/keda-olm-operator/issues/213 - [x] #215
There are new configuraiton options in KEDA Helm Charts and to KEDA in general that haven't been added to KedaController. https://github.com/kedacore/charts/tree/main/keda#configuration We should identify missing options and try to add...
At the moment the [resources file](https://github.com/kedacore/keda-olm-operator/blob/main/resources/keda.yaml ) is being loaded into the operator during the startup: https://github.com/kedacore/keda-olm-operator/blob/cbd80d4af6e95d5f0ad36af6631d3a8a008c5e3e/controllers/keda/kedacontroller_controller.go#L76-L83 It would be better to use go embed feature introduced in Go 1.16:...
Implement validating webook that check that new `KedaController CustomResource` is created in correct namespace (eg. `keda`). https://kubernetes.io/blog/2019/03/21/a-guide-to-kubernetes-admission-controllers/
When creating ScaledObject from the OCP Console, it is not possible to specify trigger-specific fields such as the `serverAddress` and the `metricName` for the Prometheus scaler. As such, it is...
On OpenShift 4.6 and higher, the operand (KedaController CR in our case) could be automatically installed when installing keda-olm-operator through OLM. We should use this http://openshift.github.io/openshift-origin-design/designs/administrator/olm/operand-creation-at-operator-install/