Skip to content
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

Timing issue when a new app is created #60

Closed
arschles opened this issue Feb 11, 2021 · 0 comments · Fixed by #116
Closed

Timing issue when a new app is created #60

arschles opened this issue Feb 11, 2021 · 0 comments · Fixed by #116
Labels
bug Something isn't working
Milestone

Comments

@arschles
Copy link
Collaborator

arschles commented Feb 11, 2021

In some cases, KEDA will attempt to ping the external scaler before it is ready to serve. In this case, KEDA doesn't seem to keep checking for at least a while (more than the 250ms that the ScaledObject indicates it should)

We should figure out either why this happens and fix it, or a backup plan would be to add logic in the operator to start up the scaler, ensure it's responsible and only then create the ScaledObject

This is possibly related to #19

@arschles arschles added the bug Something isn't working label Feb 11, 2021
@arschles arschles changed the title Timing issue when app is created Timing issue when a new app is created Feb 18, 2021
@arschles arschles added this to the Alpha 2 milestone Feb 24, 2021
kingdonb pushed a commit to kingdonb/http-add-on that referenced this issue Jun 12, 2023
…-lauw1f

Delete cluster: default/cluster-02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant