How freakynit/go-k8s works
Main Components
a) Development Environment:
• Local Go Application
• Docker Build Environment
• Local Docker Registry (k3d registry)
b) Kubernetes Cluster Components:
• K3d Cluster
• LoadBalancer
• Worker Nodes (2 agents)
• Pods running the application
• Internal Registry Service
Development Zone
• Local registry at registry.localhost:5000
Container Registry Zone
• K3d private registry
• Image tagging and pushing flow
Kubernetes Cluster Zone
• Include:
• LoadBalancer (port 8081:80)
• API Server (port 6550)
• Two worker nodes
• Deployed pods
• Internal networking
Key Flows to Represent:
Build Flow
• Source → Docker Build → Tagged Image
• Tagged Image → Local Registry Push
Deployment Flow
• Registry → K8s Cluster
• Internal Pod Distribution
Request Flow
• External Request (Port 8081) → LoadBalancer → Pods
Use these visual elements:
• Rectangles: For containers and nodes
• Blue: Development components
• Green: Registry components
• Orange: Kubernetes components
• Gray: Network boundaries
Important Details to Include:
Port Mappings
• Registry: 5000
• API: 6550
• LoadBalancer: 8081:80
Network Configurations
• localhost mappings
• Registry connections
• LoadBalancer routing
Component Labels
• Image tags (freakynit/go-k8s:1.0.0)
• Registry URLs (k3d-registry.localhost:5000)
• Service names
Level of Detail:
The external access points
Additional Notes:
• Annotations for important configuration requirements (like /etc/hosts entries)
• Relationship between the local development environment and the cluster
• Scalability aspect with the multiple worker nodes
• How to build and deploy the application
• Where the various components are located
• How the networking is configured
• How external users access the service
Remember to maintain clarity while showing the complete flow from development to deployment and external access.