XConf Architecture - EKS Auto-Scaling Setup
Admin Users/
Clients
Login/Auth
CPEs/Devices
Maintenance
Windows Trigger
Gateway/
Load Balancer
+ Istio Ingress
EKS Cluster (Ubuntu OS)
Istio Service Mesh (Traffic Mgmt, Security, Observability)
Auto-Scaling Rules
• Admin Service: 2-4 pods
• Data Service: Normal→180+ pods
• CPU Threshold: 75%
• Pod Size: t2.micro
XConf Admin
Service
Light scaling
2-4 pods max
Pods (scale 2-4)
XConf Data
Service
Heavy scaling
Normal→180+ pods
Pods (scale to 180+)
Cassandra Database
Distributed NoSQL
Configuration Data Storage
Kubernetes Control Plane
HPA (Horizontal Pod Autoscaler) • Scheduler • API Server
Auto-scaling based on CPU metrics (75% threshold)
SAT
Service
Account
Service
Tagging
Service
Device
Registry
Auto-Scaling Behavior
Normal Operations:
• Admin Service: 2 pods baseline
• Data Service: Minimal pod count
Maintenance Window:
• Admin Service: Scales to 4 pods max
• Data Service: Scales to 180+ pods
Infrastructure Specifications
Kubernetes Setup:
• Platform: Amazon EKS
• OS: Ubuntu (configurable)
• Pod Size: t2.micro instances
Service Mesh:
• Istio for traffic management, security, observability
Monitoring & Scaling
CPU Monitoring:
• Threshold: 75% CPU utilization
• HPA triggers scale-out automatically
Scale-down:
• Post-maintenance: Data service returns to normal
• Admin service: Back to 2 pod baseline