-
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
add Azure Pipelines Scaler #1706
Conversation
Thanks a ton @troydn, this is great! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good, minor comment!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks @troydn
Would be nice if you could add e2e test for this scaler.
https://github.com/kedacore/keda/tree/main/tests
I can add e2e tests for this scaler but this would require an Azure DevOps organization that can be used for the e2e tests. Should I create one and provide the details/access or would you rather provide one? |
I can set one up, what do you need? Org id and PAT? |
And what PAT permissions? |
@tomkerkhove great, just to be sure, we will need something pernament once the tests are ready. Mabye @jeffhollan or @ahmelsayed could help with that? |
They are free so should be OK! |
Org created as per kedacore/governance#20 and is up on https://dev.azure.com/kubernetes-event-driven-autoscaling/Kubernetes%20Event-driven%20Autoscaling%20(KEDA) |
Thanks! |
I'm happy to set it up, I'll create an empty pool and pipeline that has a 2 min delay in it. What else do you need in terms of config and what PAT permissions are required? |
I finished the e2e test. But I'm not sure what image should be used for the Azure DevOps Agent. For now, I used one on my docker registry. But I think this should be replaced by one on a registry managed by KEDA. The test requires an Azure DevOps environment with the following config:
|
We host all test images on https://github.com/kedacore/test-tools, are you OK in adding a container image there?
I'll get this setup tomorrow. |
@troydn I've added these GitHub secrets for you: Pipeline is up on https://dev.azure.com/kubernetes-event-driven-autoscaling/Kubernetes%20Event-driven%20Autoscaling%20(KEDA)/_build?definitionId=1 with PR open on kedacore/test-tools#11 Feel free to let me know if you're missing something. |
@tomkerkhove thanks for your help on this. I think the e2e test is ready now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, can you just fix the merge conflict please?
Signed-off-by: Troy <troydenorme@hotmail.com>
Signed-off-by: Troy <troydenorme@hotmail.com>
Signed-off-by: Troy <troydenorme@hotmail.com>
Signed-off-by: Troy <troydenorme@hotmail.com>
Signed-off-by: Troy <troydenorme@hotmail.com>
Signed-off-by: Troy <troydenorme@hotmail.com>
Signed-off-by: Troy <troydenorme@hotmail.com>
Signed-off-by: Troy <troydenorme@hotmail.com>
Signed-off-by: Troy <troydenorme@hotmail.com>
Signed-off-by: Troy <troydenorme@hotmail.com>
40e915f
to
db92875
Compare
Thank you @troydn and let me know if you are interested for the blog post! (kerkhove.tom@gmail.com) |
Add a new Azure Pipelines Scaler
Checklist
- [ ] A PR is opened to update our Helm chart (repo) (if applicable, ie. when deployment manifests are modified)Relates to #1705