Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CPU/Memory scalers not working in 2.0.0-rc #1275

Closed
knepe opened this issue Oct 20, 2020 · 5 comments
Closed

CPU/Memory scalers not working in 2.0.0-rc #1275

knepe opened this issue Oct 20, 2020 · 5 comments
Labels
bug Something isn't working

Comments

@knepe
Copy link

knepe commented Oct 20, 2020

I'm trying to test out the cpu/memory scalers, but its keda-operator does not seem to recognize it.
Im getting this in the logs:
2020-10-20T06:32:27.721Z ERROR controller Reconciler error {"reconcilerGroup": "keda.sh", "reconcilerKind": "ScaledObject", "controller": "scaledobject", "name": "scaled-obj-name", "namespace": "default", "error": "error getting scaler for trigger #0: no scaler found for type: cpu"}

I guess it might be that this #1215 is not released yet, even though it is in the docs?

Expected Behavior

CPU/Memory scalers working

Actual Behavior

CPU/Memory scalers not working

Steps to Reproduce the Problem

  1. Add ScaledObject with cpu trigger

Specifications

  • KEDA Version: v2.0.0-rc
  • Platform & Version: Please elaborate
  • Kubernetes Version: 1.16
  • Scaler(s): cpu/memory
@knepe knepe added the bug Something isn't working label Oct 20, 2020
@zroubalik
Copy link
Member

Yeah, it is not a part of RC, we are gonna release RC2 soon (in a matter of days), which will contain this scaler.

@kenotsolutions
Copy link

Yeah, it is not a part of RC, we are gonna release RC2 soon (in a matter of days), which will contain this scaler.

Thanks for the update,

I was testing and got the same error. When can you release it?

@zroubalik
Copy link
Member

@kenotsolutions once this is fixed #1257

@zroubalik
Copy link
Member

FYI RC2 is out

@bwkerbow
Copy link

bwkerbow commented Oct 23, 2020

EDIT: Never mind, I was mistaken and my issue was resolved.

I wrongly thought that the me updating KEDA from 1.5.0 to 2.0.0 broke my prometeheus scaling, but it turns out I just needed to switch my ScaledObject "apiVersion" from "keda.k8s.io/v1alpha1" to "keda.sh/v1alpha1". An article I was following used the former, but the kedacore/keda docs say to use the latter. From the keda operator logs of 2.0.0rc, it seems as though 2.0.0rc only reconciles from keda.sh whereas 1.5.0 supports reconcilation of keda.k8s.io.

Thanks for getting this CPU feature into the RC!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants