I looked into this, but ended up going with PagerDuty's Rundeck. It's a similar idea, but with a less public and more internal focus. I see it as one step beyond an active monitoring service (because of the scheduling services). We use it to aggregate scripts that rely on several disparate data sources. It's easy to create one-liners or short dependencies that are highly re-usable to and then use those to gather the right data for more complex scripts.

This service runs as an interim before we can migrate to full containers and rely on their orchestration services. Sometimes I imagine SysOps as layers, this is a Layer 7, where as K8s is all of Layers 3-5.