How splunk/docker-splunk works
Main Components
a. Container Images Layer:
• Base Images (CentOS, Debian, RedHat)
• Python Images (py23-image)
• Splunk Enterprise Images
• Universal Forwarder Images
b. Configuration Layer:
• Common Files and Apps
• Ansible Provisioning (via splunk-ansible)
• Environment Variables
• Volume Mounts
c. Deployment Scenarios:
• Standalone Deployment
• Distributed Deployment
• Kubernetes Deployment
┌─ Deployment Layer ─────────────────────────┐
• Kubernetes Orchestration │
• Docker Compose │
• Standalone Containers │
• Container Runtime Layer ──────────────────┤
• ┌─ Splunk Components ──────────────────┐ │
• Indexers │ │
• Search Heads │ │
• Cluster Master │ │
• Universal Forwarder │ │
• ┘ │
• Configuration Management Layer ───────────┤
• Ansible Provisioning │
• Environment Variables │
• Volume Mounts │
• Base Image Layer ────────────────────────┤
• CentOS/RedHat/Debian Base Images │
• Python Runtime Images │
• ┘
Key Relationships to Highlight
• How the base images are used to build the Splunk images
• Configuration flow from environment variables to container runtime
• Demonstrate how different deployment scenarios can be achieved
• Data flow between Splunk components in distributed setups
Additional Elements
• Annotations for important configuration points
• Integration points with external systems
• Version compatibility information
Deployment Scenarios
• Single instance (1so1cm.yaml)
• Clustered deployment (3idx3sh1cm.yaml)
• Kubernetes deployments (kubernetes folder scenarios)