[09:35:46] <Cyberpower678>	 Can someone remind me how long a newly created instance takes to take on the owner's SSH key?
[09:36:11] <taavi>	 Cyberpower678: maybe something like 5-10 minutes at the moment
[09:36:21] <Cyberpower678>	 Ok.  I'll wait.
[09:38:20] * Cyberpower678 is finishing the VM upgrades.
[09:38:37] <Cyberpower678>	 I kind of forgot about it when something urgent came up in the middle of the process. :/
[12:07:40] <wm-bot>	 !log tools.wd-image-positions <lucaswerkmeister> deployed 854eb65b5f (use pip-tools; updated some packages, including Flask 2.0.1 → 2.1.2)
[12:07:43] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.wd-image-positions/SAL
[12:51:15] <Cyberpower678>	 taavi: how do I remount the srv volume?
[13:01:05] <wm-bot>	 !log tools.wd-image-positions <lucaswerkmeister> deployed a37bcf7875 (proper User-Agent)
[13:01:08] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.wd-image-positions/SAL
[13:21:40] <taavi>	 Cyberpower678: if you're talking about Cinder volumes (what you see on the 'Volumes' tab on Horizon), `sudo wmcs-prepare-cinder-volume` should just work
[13:21:59] <Cyberpower678>	 taavi: no, I was referring to the legacy srv volumes
[13:22:17] <Cyberpower678>	 But it looks like that became part of the root storage.
[13:22:34] <Cyberpower678>	 You used to need role::labs::lvm::srv to get the claimed disk space
[18:44:02] <wm-bot>	 !log tools.wd-image-positions <lucaswerkmeister> deployed e48c179d47 (initial support for named place on map, can show and edit regions but not yet add statements)
[18:44:04] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.wd-image-positions/SAL
[19:04:50] <Amir1>	 so the only thing left on grid on my main toolforge project is a job that gets triggered when someone hits a certain url path in my webservice (e.g. calling a url makes the job go and clean the given article in url params). How can I migrate this to k8s? The only thing I can think of is that the url would write to a file and which a minutely cron would read and act upon but it's just too much, specially creating a pod every minutes is ewww 
[19:31:37] <RhinosF1>	 Amir1: how does it work now? How does the job actually get triggered?
[19:33:26] <Amir1>	 shell_exec
[19:34:14] <RhinosF1>	 Amir1: does that not work with toolforge-jobs submitting as a one off?
[19:34:44] <Amir1>	 no because the web service is inside a container 
[22:30:24] <wm-bb>	 <lucaswerkmeister> IIRC the webservice can theoretically create jobs (you might have to mount the k8s credentials into it, not sure), but the toolforge-jobs utility isn’t available
[22:30:30] <wm-bb>	 <lucaswerkmeister> and it’s not really a supported use case :/
[22:40:46] <AntiComposite>	 last I checked kubectl wasn't installed in the k8s pods
[22:41:29] <AntiComposite>	 and yeah in any case it's not really something you should do