-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
ScaledObject no being cached correctly at all times #4955
Comments
Any updates on this issue? We are facing a problem with a scaling of the Production instance |
The same here |
Hey I even tried to delete the helm chart of keda and install the keda from scratch but still I can see the same errors. |
I'm just wondering why I can still see errors when I already deleted all TriggerAuthentication and ScaledObject and deleted the chart of keda and all its crd . when I install keda I can see these errors in operator
while I don't have any ScaledObject in the default ns and the name of scaledObject also is empty in the log. in operator-metrics , also I can see these errors
|
We are facing the same issue. :( |
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. |
I'm facing this issue. |
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 closed due to inactivity. |
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 closed due to inactivity. |
This is a tracking issue of a bug for which a workaround has been implemented in number of places for this time until its resolved globally.
What happens
ScaledObject is sometimes not cached correctly -> for example the metrics are an empty list or the
.Status.ScaleTargetGVKR
is nilWorkaround
A workaround has been implemented in a number of places. See below.
pkg/scaling/scale_handler.go
infunc (h *scaleHandler) getTrueMetricArray()
pkg/scaling/resolver/scale_resolvers.go
infunc ResolveScaleTargetPodSpec()
Other info
initial related issue link
/kind bug
The text was updated successfully, but these errors were encountered: