Comments (6)
In any case, if keda can't create HPA, it should report status to ScaleObject (prometheus query is invalid, some parameters are invalid, etc), otherwise there is no feedback to user (who has no access to keda logs) about status of its ScaledObject
from keda.
What constitutes an error state?
from keda.
The ones I had in mind were:
- Deployment doesn't exist
- trigger connection secret doesn't exist
- bad connection to event sources (invalid connection string, password/username, not found, etc)
I think it'll make debugging issues easier if you can just lookup the status of a ScaledObject that's not behaving as you'd expect instead of going through keda logs.
from keda.
Yeah that makes sense, however bad connection to event sources is a pretty volatile and changing thing..
from keda.
This could be reflected in Status.Conditions
https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#typical-status-properties
from keda.
Fixed by #750
from keda.
Related Issues (20)
- Version 2.14 - MongoDB Atlas scheme HOT 5
- GCP Pub/Sub Scaler reports negative metric values HOT 7
- Keda 2.14 Prometheus Scaler Divides by Number of replicas of pod HOT 2
- Event Hub - incorrect metrics values HOT 6
- Dynamic Pod Scaling Based on Request Count HOT 1
- External scaler connection errors ignored, the HPA is missing metrics HOT 4
- Github Runner Scaler doesn't trigger until all job environments are approved
- Report the use of components with vulnerabilities in keda HOT 1
- Getting " no matches for kind "TriggerAuthentication" in version "keda.k8s.io/v1alpha1" ensure CRDs are installed first" while spplying scaledobject for Keda HOT 1
- leaderelection.go:320] error retrieving resource lock keda/operator.keda.sh: invalid character ', after object key HOT 3
- minReplicaCount not applied on a trigger type: cron
- GCP Stackdriver scaler doesn't work with centralized metrics scope project HOT 2
- Refactor Scalers with new declarative scaler config HOT 3
- After completing a task, the Pod consistently enters the CrashLoopBackOff state repeatedly with the same Pod. HOT 1
- Upgrade KEDA to use Debian 12 Distroless
- Add support for Cassandra TLS auth
- desiredReplicas ignored in scaledObject with trigger cron HOT 4
- Scaler not being properly closed HOT 1
- Add Scaler that Read Metrics From Current Custom Metrics Adapter HOT 3
- Keda operator pod restarts because of objectScaler HOT 5
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from keda.