other question, to be honest my project is a uptime kuma like : should I create one deployement for all probes (where each probe is a website as example) or as much deployment than website to probe ?

I would create one - run it with the url as param

not sure to understand

one deployment - pass the url's you want to http check as a param

but the url could be add or removed / updated on the fly by tenants / customers so I must either 1 : create one global deployment which will get urls from a database then create N number of tasks, 2 : one deployment per url with the url as params

No worries - you can dynamically create the flow runs though

yeah I know, my goal is to schedule probing website every minutes (or 30s, 2mn, etc), not create them from another source

how many different urls?

ptentially thousands

its actually interesting as I am doing something similar with puppeteer - SASS synthetics are expensive at scale

also with 1 deploy per urls I would load balacing across multiples nodes the work of probing urls

a deployment per url seems very excessive and hard to maintain - I would have a single deployment which wakes on a schedule and picks the next n urls to test from a queue/db table

for now i's a personnal project, Ididn't even writted any line of code

you can have the schedule to fire every second - the agent will pick up 10 scheduled flows at once and spin up 10 k8s pods to do the work

my target is to do an http req for each url every minutes

yeah, its an interesting problem with a good few ways to tackle it