-
Notifications
You must be signed in to change notification settings - Fork 90
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
Flux v2 reconciler is not working correctly for HTTPScaledObject #1054
Comments
Hello, You have to choose between
|
Hi @JorTurFer Still getting the message: kind: HTTPScaledObject
apiVersion: http.keda.sh/v1alpha1
metadata:
name: http-scaledobject-orderapplication
namespace: daprpoc
spec:
hosts:
- dev-app-ordersample.example.be
pathPrefixes:
- /
scaleTargetRef:
name: orderapplication
kind: Deployment
apiVersion: apps/v1
service: orderapplication-svc
port: 80
replicas:
min: 0 # We want to scale to zero eventually
max: 10
scaledownPeriod: 300
scalingMetric: # requestRate and concurrency are mutually exclusive
# requestRate:
# granularity: 1s
# targetValue: 100
# window: 1m
concurrency:
targetValue: 100 |
Anything related? #611 |
Sorry for the slow response, I've been involved on a huge working peak :( |
I'd like to see the error of the 1st pod: |
|
Mb, I need the other container ( |
Report
Flux v2 on an AKS 1.29.4.
Flux reports the following error:
Current YAML manifest:
reports the following:
Expected Behavior
Reconciliation to work correctly
Actual Behavior
Health check on HTTPScaledObject failed
Steps to Reproduce the Problem
Logs from KEDA HTTP operator
PS: it's only the http-scaledobject-orderapplication that does not report correctly
HTTP Add-on Version
0.8.0
Kubernetes Version
1.29
Platform
Microsoft Azure
Anything else?
The text was updated successfully, but these errors were encountered: