Overall with the push to move all SCB services to kubernetes this fiscal year this is bound anyway to happen as the entire SCB is meant to be fully decomissioned. It's a nice clean up, I just had it on the backburner since there is no real compelling reason to do it.
Now, as far as using it as a fallback in case the kubernetes cluster gravely misbehaves, it would take us some work to revert back to using the scb cluster and given discovery works quite well for depooling an entire DC I think we don't really need keeping mathoid deployed on scb as an extra protection mechanism.
But alas, there is also the deployment-prep case. Where we still need to support this, so I guess we are stuck with it for now
Unfortunately MediaWiki is still expecting the VM to exist:
wmf-config/LabsServices.php: 'mathoid' => 'http://deployment-mathoid.eqiad.wmflabs:10042',
The two hosts with that role are deployment-eventgate-analytics-1 and deployment-sessionstore01 so neither of them are really appropriate for this, plus they both run jessie.
The jessie part is probably irrelevant (why are they jessie? I have no idea.) since the software itself is embedded in a stretch container. But in theory, a VM with more or less the same configuration as the ones above (I think the latter was created copying the former), should work.