How jenkins-infra/kubernetes-management works
Main Components
a) Cluster Layer:
• Different Kubernetes clusters (cijioagents1, cijioagents2, infracijioagents1, privatek8s, publick8s)
b) Configuration Management Layer:
• Helmfile deployments (from /clusters directory)
• Helm charts configuration (from /config directory)
• Secrets management with SOPS integration
• UpdateCLI automation system
c) External Services Layer:
• Azure Key Vault (for secrets)
• GitHub (for source code and secrets repository)
• Docker Registry (for container images)
• Cloud Providers (Azure, AWS, DigitalOcean - indicated by az, awscli, doctl requirements)
Component Relationships
• Helmfile → Kubernetes Clusters (deployment flow)
• UpdateCLI → GitHub (version updates)
• SOPS ↔ Azure Key Vault (secrets encryption/decryption)
• Clusters ↔ External Services (service dependencies)
Specific Implementation Details
Specialized components for:
• Jenkins Controllers (multiple instances per cluster)
• Ingress Controllers (both public and private nginx)
• Service-specific configurations (like accountapp, keycloak, LDAP, etc.)
• Monitoring solutions (Datadog, indicated by datadog.yaml files)
Infrastructure Layer (Bottom)
• Kubernetes clusters
• Cloud providers
• Storage systems
Configuration Layer (Middle)
• Helm charts
• Configuration files
• Secrets management
Automation Layer (Top)
• UpdateCLI
• CI/CD pipelines
• Monitoring and logging
Important Notes
• Version control flow showing how updates propagate
• Security boundaries and access controls
• High-availability setups where applicable
• Public vs. private network boundaries