workflow-management

Overview

• Namespace: workflow-management
• Purpose: n8n Workflow Automation Platform - PRODUCTION
• Age: ~644 days
• Status: Active - Workflow automation and integration
• Workloads: 1 deployment (1 replica)
• Environment: PRODUCTION - Business process automation

Architecture

n8n workflow automation platform:

• Deployment: Single workflow-management pod (1 replica)
• External Access: LoadBalancer service on 34.124.238.59:5678
• Purpose: Visual workflow builder and automation tool

Auto-Scaling Configuration

Not Applicable:

• Single replica (no HPA configured)
• Fixed 1 replica
• LoadBalancer for external access

Workload Categories

Workflow Automation (1 deployment)

Name	Replicas	Status	Purpose
workflow-management	1/1	Running	n8n workflow automation

Services

Name	Type	Cluster IP	External IP	Ports	Purpose
workflow-management	LoadBalancer	10.8.25.197	34.124.238.59	5678:30550	n8n web interface

Access & Management

View all resources:

kubectl get all -n workflow-management

Access n8n:

# Direct access via LoadBalancer
# Access: http://34.124.238.59:5678

# Or via kubectl port-forward
kubectl port-forward -n workflow-management service/workflow-management 5678:5678
# Access: http://localhost:5678

Check pod status:

# View pod
kubectl get pods -n workflow-management

# View logs
kubectl logs -f deployment/workflow-management -n workflow-management

# Check for errors
kubectl logs deployment/workflow-management -n workflow-management --tail=100 | grep -i "error"

Restart service:

kubectl rollout restart deployment/workflow-management -n workflow-management

Monitoring

Pod metrics:

kubectl top pods -n workflow-management

# Check pod resource usage
kubectl describe pod -n workflow-management | grep -A 5 "Requests\|Limits"

Events:

kubectl get events -n workflow-management --sort-by='.lastTimestamp' | head -20

Data Flow

Users/External Systems
    ↓
LoadBalancer (34.124.238.59:5678)
    ↓
workflow-management pod (n8n)
    ↓
External APIs/Services
    ↓
Target Systems (Integrations)

n8n Workflow Platform

1. Workflow Automation

• Visual workflow builder (1 replica)
• Drag-and-drop interface
• 200+ integrations available
• Webhook support
• Scheduled execution

2. External Access

• LoadBalancer on 34.124.238.59:5678
• Web-based interface
• REST API endpoints
• Webhook receivers

3. Integration Capabilities

• HTTP requests
• Database connections
• API integrations
• Email notifications
• Slack, Teams, etc.
• Custom JavaScript/Python code

Production Considerations

High Availability

Single Point of Failure:

• 1 replica (No HA)
• Pod restart = temporary unavailability
• No redundancy

Recommendations

1. High Availability (Optional):

   • Current: 1 replica (acceptable for non-critical automation)
   • Consider 2+ replicas if workflows are business-critical
   • Would require shared storage or database backend

2. Backup Strategy:

   • Export workflows regularly
   • Backup n8n database/storage
   • Document critical workflows
   • Version control workflow definitions

3. Monitoring:

   • Monitor pod health
   • Alert on pod failures
   • Track workflow execution success rates
   • Monitor webhook endpoints

4. Resource Limits:

   • Set appropriate CPU/memory limits
   • Monitor resource usage over time
   • Scale resources based on workflow complexity

5. Security:

   • LoadBalancer exposed to internet
   • Ensure authentication is enabled
   • Use HTTPS for external access
   • Review firewall rules
   • Audit workflow access and permissions

Troubleshooting

n8n not accessible:

# Check pod status
kubectl get pods -n workflow-management

# Check service
kubectl get svc -n workflow-management

# Test LoadBalancer
curl http://34.124.238.59:5678/healthz

# Check logs
kubectl logs -f deployment/workflow-management -n workflow-management

Workflow execution issues:

# Check pod logs
kubectl logs deployment/workflow-management -n workflow-management --tail=100

# Check for errors
kubectl logs deployment/workflow-management -n workflow-management | grep -i "error\|fail"

# Restart pod
kubectl rollout restart deployment/workflow-management -n workflow-management

Performance issues:

# Check resource usage
kubectl top pod -n workflow-management

# Check pod events
kubectl describe pod -n workflow-management

# Check resource limits
kubectl describe deployment workflow-management -n workflow-management | grep -A 10 "Limits\|Requests"

Performance Metrics

Current Scale

• Deployment: 1 replica
• Age: ~644 days (stable)
• Recent Update: 82 days ago
• External Access: LoadBalancer IP 34.124.238.59:5678

Stability

• Pod Age: 82 days (stable)
• Restarts: Check with kubectl get pods -n workflow-management
• Critical Role: Business process automation
• Single Point of Failure: Yes (1 replica)

Architecture Notes

• n8n Platform: Open-source workflow automation
• External Access: LoadBalancer for web interface
• Integration Hub: Connects multiple systems
• No HA: Single replica deployment
• Long Running: Pod stability is critical for ongoing workflows