-
Notifications
You must be signed in to change notification settings - Fork 449
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
Added documentation for Azure Pipelines Demands #685
Conversation
✅ Deploy Preview for keda ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
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.
Made some editorial suggestions to make it easier to read and remove the direct references to ScaledJob since you can also use it with ScaledObject
|
||
#### How it works under the hood. | ||
|
||
Azure Devops has a Job Request API with returns a list of all agents which can potentially match up to the Queued Job. KEDA will scan this request to find any matching template from the defined parent in the ScaledJob definition. Once it finds it, it will spin up a ScaledJob that matched the definition and Azure DevOps will assign to that agent. |
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.
Can we add a link to the API?
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.
This is a bit of aa weird one. I'm using the same API that keda has always used, but this API is actually not disclosed by Microsoft. There API stops at /pool/id; there is a deeper internal API which is /pool/id/JobRequests. This is undocumented on the MS site I believe; hence as I can't publish an official link, should be left out.
authenticationRef: | ||
name: pipeline-trigger-auth | ||
``` | ||
###Example for Parent Deployment or StatefulSet |
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.
I'm not sure about having the requirement of an agent for doing nothing TBH. I prefer to register the agent manually in the AzDO UI than creating a deployment only for that.
WDYT @kedacore/keda-contributors ?
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.
The reason I use a deployment and then delete it after it has registered in ADO using my CD pipelines is that I can change versions of packages, do upgrades so the capabilities of the agent do change over time. Maintaining a large number of different agents in my build farm works this way. I see no reason why you couldn't do either way though.
Maybe a podspec would be better?
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.
My concern is that you have your own business logic to manage this and it works with your use case, but it's managed by your side, not by KEDA. IMO, we should be most agnostics as possible and use the upstream tools for doing the upstream things. Obviously, we can add a "tip" suggesting the approach, having to deploy (and potentially delete) the deployment only to upgrade the agent in AzDO could be a complex action if you only have 2-3 different agents.
Maybe I'm overthinking about this and that's why I'd like to get the opinion of other @kedacore/keda-contributors but it's more a thing about how we document the feature than an issue with the feature itself (In fact, it's already approved :) ).
@Eldarrin |
@JorTurFer Conversation 1, I can resolve if your happy that that the API is undocumented on the MS side. Conversation 2, I thought you were waiting for comments from other contributors? But can resolve |
Let's solve the first point, and we can open another issue to improve this in the future, but at least next release will have this feature |
Please, solve also the signing issue in your commits 🙏 |
Signed-off-by: mortx <mortxbox@live.com>
Signed-off-by: mortx <mortxbox@live.com>
Signed-off-by: mortx <mortxbox@live.com>
Signed-off-by: mortx <mortxbox@live.com>
Signed-off-by: mortx <mortxbox@live.com>
Signed-off-by: mortx <mortxbox@live.com>
Signed-off-by: mortx <mortxbox@live.com>
Signed-off-by: mortx <mortxbox@live.com>
Signed-off-by: mortx <mortxbox@live.com>
Signed-off-by: mortx <mortxbox@live.com>
Signed-off-by: mortx <mortxbox@live.com>
Signed-off-by: mortx <mortxbox@live.com>
Signed-off-by: Patrice Chalin <pchalin@gmail.com> Signed-off-by: mortx <mortxbox@live.com>
Signed-off-by: mortx <mortxbox@live.com>
…#815) Signed-off-by: mortx <mortxbox@live.com>
…er (#811) Signed-off-by: Jorge Turrado <jorge_turrado@hotmail.es> Signed-off-by: mortx <mortxbox@live.com>
Signed-off-by: Zbynek Roubalik <zroubalik@gmail.com> Signed-off-by: mortx <mortxbox@live.com>
…812) Signed-off-by: Jorge Turrado <jorge_turrado@hotmail.es> Signed-off-by: mortx <mortxbox@live.com>
Signed-off-by: Zbynek Roubalik <zroubalik@gmail.com> Signed-off-by: mortx <mortxbox@live.com>
Signed-off-by: Jonas Bentz <Jonas-Bentz@gmx.de> Signed-off-by: mortx <mortxbox@live.com>
Signed-off-by: Zbynek Roubalik <zroubalik@gmail.com> Signed-off-by: mortx <mortxbox@live.com>
…824) Signed-off-by: mortx <mortxbox@live.com>
Signed-off-by: Zbynek Roubalik <zroubalik@gmail.com> Signed-off-by: mortx <mortxbox@live.com>
…aler (#823) Signed-off-by: mortx <mortxbox@live.com>
Signed-off-by: mortx <mortxbox@live.com>
…#826) Signed-off-by: mortx <mortxbox@live.com>
Signed-off-by: Joe Bowbeer <joe.bowbeer@gmail.com> Signed-off-by: mortx <mortxbox@live.com>
…kload Scaler (#828) Signed-off-by: mortx <mortxbox@live.com>
…enstack metrics Scalers (#829) Signed-off-by: mortx <mortxbox@live.com>
Signed-off-by: mortx <mortxbox@live.com>
…835) Signed-off-by: mortx <mortxbox@live.com>
…834) Signed-off-by: mortx <mortxbox@live.com>
#838) Signed-off-by: mortx <mortxbox@live.com>
#843) Signed-off-by: mortx <mortxbox@live.com>
…t Scaler (#841) Signed-off-by: mortx <mortxbox@live.com>
.... abandon pr and start over? followed the instructions to rebase and it blew up |
Maybe squashing the branch, you could solve it. If not, feel free to close this and open another |
Closing to re-add just azure_pipelines.md as new PR |
Signed-off-by: mortx mortxbox@live.com
Documents using parents to support demands in ADO
Checklist
Relates to kedacore/keda#2328
Relates to kedacore/keda#2795