Active field from kubectl get httpscaledobject is always empty

[josegonzalez]

Report

The "Active" field appears to be queried incorrectly, causing it to always be empty.

http-add-on/config/crd/bases/http.keda.sh_httpscaledobjects.yaml

Line 35 in 45f645f

- jsonPath: .status.conditions[?(@.type=="HTTPScaledObjectIsReady")].status

 .status.conditions[?(@.type=="HTTPScaledObjectIsReady")].status

Is the query, but the type is never that value. Instead, that is the reason:

status:
  conditions:
  - message: Identified HTTPScaledObject creation signal
    reason: PendingCreation
    status: Unknown
    timestamp: "2024-12-11T00:59:45Z"
    type: Ready
  - message: Finished object creation
    reason: HTTPScaledObjectIsReady
    status: "True"
    timestamp: "2024-12-11T00:59:45Z"
    type: Ready

Expected Behavior

Either a value of "True" or "False"

Actual Behavior

Empty value

Steps to Reproduce the Problem

1. Create any HTTPScaledObject
2. Call kubectl get HTTPScaledObject
3. See that the value under the Active column is empty.

Logs from KEDA HTTP operator

n/a

HTTP Add-on Version

0.8.0

Kubernetes Version

1.30

Platform

Other

Anything else?

No response

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

[wozniakjan]

thanks for the bug report, looks like this has been the case ever since the project was started, somehow the condition type is always ready for everything and then the reason contains relevant condition type names with status having information regarding reason type. I guess for now it's safe to completely ignore the type as that carries no relevant information.

I will at least fix the jsonpath for that kubectl command.

[josegonzalez]

Cool, thats really all I cared about. Thanks!