What do you think about this option (in case I have many partners and each can connects several products(taps)) Create a folder with schedules and when some client appears, I add a new file to the folder and the file name is partner_id_tap_name.yml Inside the file will be - name: partner_id_tap_name_sync interval: '*/15 * * * *' job: tap-name-to-big-query env: TAP_NAME_USERNAME: "username" TAP_NAME_PASSWORD: "password" Then in meltano.yml I import all these files that exist. I am confused by the fact that there will be several thousand such files when the partner deletes the product, I will need to look for the file and delete it. But thanks to this, it seems that I can get rid of kubernets. What do you think about this? In general, is it normal if there are several thousand schedules in the schedules list? And the second side effect - it seems not very good that when some partner adds a product I have to rebuild the entire meltano project (but it's less expensive than deploying a new instance every time?) I actually came up with this idea when I saw that I can import a folder with yml files into another yaml file.