Report

The HTTPScaledObject resource does not work with Flux. Flux waits for the HTTPScaledObject to have a status of Ready. However, the HTTPScaledObject CRD has three conditions with the type of Ready:

• message: Identified HTTPScaledObject creation signal
  reason: PendingCreation
  status: Unknown
  timestamp: "2025-12-05T18:52:42Z"
  type: Ready
• message: App ScaledObject created
  reason: AppScaledObjectCreated
  status: "True"
  timestamp: "2025-12-05T18:52:42Z"
  type: Ready
  • message: Finished object creation
    reason: HTTPScaledObjectIsReady
    status: "True"
    timestamp: "2025-12-05T18:52:42Z"
    type: Ready

Flux's default health check for custom resources expects a single Ready condition with status: True.

Expected Behavior

A Flux Kustomization resource which manages HTTPScaledObject to reconcile with that status Ready: True

Actual Behavior

NAMESPACE                               NAME                                         AGE     READY     STATUS
example                                     example                               42d     False     health check failed after 3m0.019918732s: timeout waiting for: [HTTPScaledObject/example/example status: 'InProgress']

Steps to Reproduce the Problem

1. Install Flux on a cluster
2. Create a Flux module with HTTPScaledObject
3. Deploy the module with a Flux Kustomization resource

Logs from KEDA HTTP operator

Logs show no errors

HTTP Add-on Version

0.11.1

Kubernetes Version

Other

Platform

Amazon Web Services

Anything else?

Kubernetes version 1.34