keda-operator error after deployment

[alexakr]

I installed keda-operator on Kubernetes 1.15 using Helm 2 helm install kedacore/keda command.
In the log file there is the following error:
{"level":"info","ts":1589781448.036523,"logger":"cmd","msg":"KEDA Version: 1.4.1"}
{"level":"info","ts":1589781448.0365922,"logger":"cmd","msg":"Go Version: go1.13.3"}
{"level":"info","ts":1589781448.0366158,"logger":"cmd","msg":"Go OS/Arch: linux/amd64"}
{"level":"info","ts":1589781448.0366275,"logger":"cmd","msg":"Version of operator-sdk: v0.11.0"}
{"level":"info","ts":1589781448.03694,"logger":"leader","msg":"Trying to become the leader."}
{"level":"info","ts":1589781448.357414,"logger":"leader","msg":"Found existing lock with my name. I was likely restarted."}
{"level":"info","ts":1589781448.357453,"logger":"leader","msg":"Continuing as the leader."}
{"level":"info","ts":1589781448.661053,"logger":"controller-runtime.metrics","msg":"metrics server is starting to listen","addr":"0.0.0.0:8383"}
{"level":"info","ts":1589781448.6612098,"logger":"cmd","msg":"Registering Components."}
{"level":"info","ts":1589781448.6614869,"logger":"controller-runtime.controller","msg":"Starting EventSource","controller":"scaledobject-controller","source":"kind source: /, Kind="}
{"level":"error","ts":1589781450.4600754,"logger":"controller-runtime.source","msg":"if kind is a CRD, it should be installed before calling Start","kind":"ScaledObject.keda.k8s.io","error":"no matches for kind "ScaledObject" in version "keda.k8s.io/v1alpha1"","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-logr/zapr@v0.1.1/zapr.go:128\nsigs.k8s.io/controller-runtime/pkg/source.(*Kind).Start\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.2.2/pkg/source/source.go:88\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Watch\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.2.2/pkg/internal/controller/controller.go:122\ngithub.com/kedacore/keda/pkg/controller/scaledobject.add\n\tkeda/pkg/controller/scaledobject/scaledobject_controller.go:59\ngithub.com/kedacore/keda/pkg/controller/scaledobject.Add\n\tkeda/pkg/controller/scaledobject/scaledobject_controller.go:42\ngithub.com/kedacore/keda/pkg/controller.AddToManager\n\tkeda/pkg/controller/controller.go:13\nmain.main\n\tkeda/cmd/manager/main.go:114\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:203"}
{"level":"error","ts":1589781450.4601953,"logger":"cmd","msg":"","error":"no matches for kind "ScaledObject" in version "keda.k8s.io/v1alpha1"","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-logr/zapr@v0.1.1/zapr.go:128\nmain.main\n\tkeda/cmd/manager/main.go:115\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:203"}

[zroubalik]

Seems like ScaledObject CRD was not installed during the chart installation. Could you please try to uninstall keda and install it once again, to check whether there are any issues during the installation? After the installation please check that KEDA CRDs are installed in the cluster:
kubectl get crds | grep keda

[alexakr]

There are no errors during Helm deployment, but KEDA CRDs are not installed.

NAME REVISION UPDATED STATUS CHART NAMESPACE
keda 1 Mon May 18 11:44:14 2020 DEPLOYED keda-1.4.1 keda

[alexakr]

So I assume this is a bug since Helm should install KEDA CRDs as well.

[grv-trip]

@alexakr did you try to install CRD's using kubectl apply -f <<crd_file>> if they didn't come up using helm chart?

[alexakr]

Yes, of course. This is the workaround, but the helm chart must be fixed to install the CRDs as well.

[grv-trip]

Interestingly... for me, CRD's came up as expected when I deployed the keda operator using helm chart. But I used Helm 3

[tomkerkhove]

Can you try if this is still the case with our rc2 please @alexakr ?

[alexakr]

This case is for Helm 2.
But from rc2 breaking changes: "Removed support for Helm 2.x".
And according to @grv-trip it worked with Helm 3 anyway. So I suppose rc2 is not relevant for this issue.

[tomkerkhove]

Ok, hope this won't be too much of a hassle to use Helm 3 but given the Helm 2 deprecation timeline we are removing it with this new major version, sorry.