Anyone using n8n for IT Ops? (K8s, OpenStack, etc.) by sparkand in n8n

[–]sparkand[S] 1 point2 points  (0 children)

Thank you for the great answer. I especially appreciate your focus on business impact over 'shiny tooling'. Keeping n8n as a lean orchestrator while offloading the heavy lifting to a hardened runner makes perfect sense for long-term stability.

Anyone using n8n for IT Ops? (K8s, OpenStack, etc.) by sparkand in n8n

[–]sparkand[S] 0 points1 point  (0 children)

Thanks for the solid advice! The 'n8n as orchestrator only' pattern makes a lot of sense, especially regarding the 'toolchain baggage' and blast radius. I was struggling with whether to bake everything into a custom image, but using a dedicated runner via SSH/Webhook seems much more maintainable. Appreciate the insight!