The webserver itself was migrated to Kubernetes with:

ssh valeriobozzolan@login-buster.toolforge.org
become itwiki
webservice stop
webservice --backend=kubernetes php7.2 start

I handled the tasks in Python, hopefully everything works fine.

I've migrated my children to Kubernetes. Here some notes.

Script markadmins

From:

5 * * * * jsub -once -N itwiki-markadmins -o $HOME/markadmins/log.out -e $HOME/markadmins/log.err $HOME/markadmins/bot.php >/dev/null 2>&1

To:

toolforge-jobs run itwiki-markadmins --command ./markadmins/bot.php --image tf-php74 --schedule "5 * * * *"

Script orphanizerbot

From:

*/3 * * * * /usr/bin/jsub -N cron-52 -once -quiet $HOME/orphanizerbot/start-in-toolforge.sh

...
./orphanizerbot/orphanize.php \
--warmup=120 \
--delay=9 \
--cooldown=50 \
--no-interaction

To:

toolforge-jobs run itwiki-orphanizerbot --command "./orphanizerbot/orphanize.php --warmup=120 --delay=9 --cooldown=50 --no-interaction" --image tf-php74 --schedule "*/3 * * * *"

Script deletionbot

From:

*/8 * * * * /usr/bin/jsub -N cron-37 -once -quiet $HOME/deletionbot/start-in-toolforge.sh

...
./deletionbot/bot.php --days=11

To:

toolforge-jobs run itwiki-deletionbot --command "./deletionbot/bot.php --days=11" --image tf-php74 --schedule "*/8 * * * *"

For now it seems everything is OK and with a very simple and smooth migration, without any minimal trouble of any kind. Wow.

Let's see tomorrow morning if everything is on fire.

It's not clear to me if the toolforge-jobs command in its automagic features also persists the --schedule also after a reboot of the tools-sgebastion-10 itself or not. I'm positive BTW.

In T305334#7839532, @valerio.bozzolan wrote:

It's not clear to me if the toolforge-jobs command in its automagic features also persists the --schedule also after a reboot of the tools-sgebastion-10 itself or not. I'm positive BTW.

It functions independently of the bastion. You can see the stored jobs, including the schedule, with toolforge-jobs list (add --long for more info).

OK so that's a view of the stored jobs not a view of the jobs planned in the current "session or whatever temporary". Thank you. That's awesome!