INFO - Empty response for errors with kubectl and helm

We noticed that some of our customers are having questions about the error messages they’re getting when deploying their workload using helm and/or using kubectl:

E0228 08:25:03.223480   19443 memcache.go:255] couldn't get resource list for Got empty response for:

The problem is related to an update in change of behavior in the kubernetes client-go library (1.26+). But because our Keda exposes the by default, it returns an empty resource list.

Therefore the solution for now is to:

We’ve updated our documentation and made the requirements more specific.

There are currently several upstream discussions going on regarding this matter:

We’ll be watching those upstream conversations closely and keep you posted in case there’s a change.