Automated Kubernetes testing with Robot Framework, ArgoCD & with KinD lifecycle
UnknownWhat this workflow does
This workflow has 54 nodes and runs on a schedule (every day at 01:00) (plus 2 other triggers). Along the way it connects GitLab, Telegram and Robotframework (community).
How it runs
Trigger: On a schedule (every day at 01:00) (plus 2 other triggers).
- Set Parameters (Edit Fields (Set)): sets 9 fields: target_host, target_port, target_user…
- Switch: routes items into 3 branches
- Check Sshpass Exist Local (Execute Command): runs a shell command on the n8n host
- Get a file - ROBOT Script (GitLab): get (file)
- Check Sshpass Exist Local (D) (Execute Command): runs a shell command on the n8n host
- Is Installed Local? (If): checks a condition and branches into true / false
- Write Dowloaded ROBOT Script (Read/Write Files from Disk): writes a file to disk
- Is Installed Local? (D) (If): checks a condition and branches into true / false
- Check Docker on Target (Execute Command): runs a shell command on the n8n host
- Install Sshpass Local (Execute Command): runs a shell command on the n8n host
…plus 40 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
We can't fully verify this one: it relies on 1 community package, and n8n 3.0 turns unverified community packages off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).
- Check that n8n-nodes-robotframework is verified or supports 3.0 (used in Robot Framework).
Nodes used (12)
- Manual Trigger
n8n-nodes-base.manualTrigger - Webhook
n8n-nodes-base.webhook - Schedule Trigger
n8n-nodes-base.scheduleTrigger - GitLab
n8n-nodes-base.gitlab - Edit Fields (Set)
n8n-nodes-base.set - Robot Framework
n8n-nodes-robotframework.robotFramework - Switch
n8n-nodes-base.switch - Read/Write Files from Disk
n8n-nodes-base.readWriteFile - Execute Command
n8n-nodes-base.executeCommand - Telegram
n8n-nodes-base.telegram - If
n8n-nodes-base.if - No Operation, do nothing
n8n-nodes-base.noOp
From the author
Overview This n8n workflow provides automated CI/CD testing for Kubernetes applications using KinD (Kubernetes in Docker). It creates temporary infrastructure, runs tests, and cleans up everything automatically. --- Three-Phase Lifecycle INIT Phase -…