Open hochuenw-dd opened 2 years ago
mmm, this is interesting, but I don't see it as part of KEDA in the cluster, but I think is a good starting point for a cli (because basically it's a troubleshooting/debbuging thing). WDYT @kedacore/keda-contributors ?
I'm not sure how much we can cover on this, we could introduce a log message providing the schedule with expected replica count but everything beyond that would be around tooling.
I think a CLI would be useful here, but we don't have one today
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.
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.
Proposal
When cron schedules get complicated, it's harder for users to see and understand what's the expected replica counts (cron schedule) for a given service by looking at the cron schedules in the scaledobject.
Use-Case
For example,
Does it make sense to create a metric to visualize future expected replica counts for predictive-based scalers such as cron scaler.
Anything else?
No response