External access to services via configured domain names (using ${DOMAIN})
Internal-only access to admin interfaces (via internal.${DOMAIN} subdomains)
Secure traffic routing with automatic TLS
Reliable networking with proper load balancing

Service Management

Wild Cloud uses a streamlined per-service setup approach:

Primary Command: wild-service-setup <service> [options]

Default: Configure and deploy service using existing templates
--fetch: Fetch fresh templates before setup (for updates)
--no-deploy: Configure only, skip deployment (for planning)

Master Orchestrator: wild-setup-services

Sets up all services in proper dependency order
Each service validates its prerequisites before deployment
Fail-fast approach with clear recovery instructions

Architecture

Internet → External DNS → MetalLB LoadBalancer → Traefik → Kubernetes Services
                                    ↑
                                 Internal DNS
                                    ↑
                              Internal Network

Key Components

MetalLB - Provides load balancing for bare metal clusters
Traefik - Handles ingress traffic, TLS termination, and routing
cert-manager - Manages TLS certificates
CoreDNS - Provides DNS resolution for services
ExternalDNS - Automatic DNS record management
Longhorn - Distributed storage system for persistent volumes
NFS - Network file system for shared media storage (optional)
Kubernetes Dashboard - Web UI for cluster management (accessible via https://dashboard.internal.${DOMAIN})
Docker Registry - Private container registry for custom images
Utils - Cluster utilities and debugging tools

Common Usage Patterns

Complete Infrastructure Setup

# All services with fresh templates (recommended for first-time setup)
wild-setup-services --fetch

# All services using existing templates (fastest)
wild-setup-services

# Configure all services but don't deploy (for planning)
wild-setup-services --no-deploy

Individual Service Management

# Most common - reconfigure and deploy existing service
wild-service-setup cert-manager

# Get fresh templates and deploy (for updates)
wild-service-setup cert-manager --fetch

# Configure only, don't deploy (for planning)
wild-service-setup cert-manager --no-deploy

# Fresh templates + configure + deploy
wild-service-setup cert-manager --fetch

Service Dependencies

Services are automatically deployed in dependency order:

metallb → Load balancing foundation
traefik → Ingress (requires metallb)
cert-manager → TLS certificates (requires traefik)
externaldns → DNS automation (requires cert-manager)
kubernetes-dashboard → Admin UI (requires cert-manager)

Each service validates its dependencies before deployment.

Idempotent Design

All setup is designed to be idempotent and reliable:

Atomic Operations: Each service handles its complete lifecycle
Dependency Validation: Services check prerequisites before deployment
Error Recovery: Failed services can be individually fixed and re-run
Safe Retries: Operations can be repeated without harm
Incremental Updates: Configuration changes applied cleanly

Example recovery from cert-manager failure:

# Fix the issue, then resume
wild-service-setup cert-manager --fetch
# Continue with remaining services
wild-service-setup externaldns --fetch