Kubernetes deployment & pod monitoring with Telegram alerts
Needs changesNeeds changes. This template uses 1 thing(s) that n8n 3.0 removes: Write Binary File. 1 breaking item(s) found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 8 nodes and runs on a schedule (every minute). Along the way it connects Telegram.
How it runs
Trigger: On a schedule (every minute).
- Kubeconfig Setup (Code): runs custom JavaScript code
- Get Pods (Execute Command): runs a shell command on the n8n host
- Get Deployments (Execute Command): runs a shell command on the n8n host
- Process & Generate Report (Code): runs custom JavaScript code
- Has Alerts? (If): checks a condition and branches into true / false
- Send Telegram Alert (Telegram): uses Telegram
- Save Report (Write Binary File): uses Write Binary File
Services it uses
Before you upgrade to n8n 3.0
1 thing in this workflow is removed in n8n 3.0. Fix it before you upgrade:
- Write Binary File in Save Report: replace with Read/Write Files from Disk.
| Removed in 3.0 | Replace with |
|---|---|
| Write Binary File Save Report | Read/Write Files from Disk |
Nodes used (6)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Code
n8n-nodes-base.code - Execute Command
n8n-nodes-base.executeCommand - If
n8n-nodes-base.if - Telegram
n8n-nodes-base.telegram - Write Binary File
n8n-nodes-base.writeBinaryFile
From the author
SETUP INSTRUCTIONS 1. Configure Kubeconfig - Open the "Kubeconfig Setup" node - Paste your entire kubeconfig file content into the kubeconfigContent variable - Set your target namespace in the namespace variable (default: 'production') Example kubeconfig…