How chrishirsch/kuberhealthy-storage-check works
Main Components
a) Core Components:
• Kuberhealthy Storage Check Controller
• Storage Check Job Creator
• PVC (Persistent Volume Claim) Manager
• Node Discovery Service
• Storage Initialization Job
• Storage Validation Job
b) External Dependencies:
• Kubernetes API Server
• Storage Provider (e.g., VMware vSAN)
• Parent Kuberhealthy System
┌─────────────────────────────────────┐
• Kuberhealthy System │
• ┬───────────────────┘
• ↓
┌─────────────────────────────────────┐
• Storage Check Controller │
• ┬───────────────────┘
• ↓
┌─────────────────────────────────────┐
• Execution Pipeline │
• ┘
┌──────────────┐ ┌──────────────┐ ┌──────────────┐
• Cleanup Old │ → │Create & Bind │ → │Initialize │
• Resources │ │PVC │ │Storage │
• ┘ └──────────────┘ └──────────────┘
• ↓ ↓
┌──────────────┐ ┌──────────────┐ ┌──────────────┐
• Node Discovery│ ← │Validate │ ← │Create Check │
• & Filtering │ │Storage │ │Jobs │
• ┘ └──────────────┘ └──────────────┘
Important Elements to Highlight
• Hexagons: External services
Specific Details
a) Configuration Options:
• Resource limits
• Security context settings
b) Integration Points:
• Kubernetes API interactions
• Storage class integration
• Node selection logic
Technical Details
• Default values (CPU: 15m, Memory: 20Mi)
• Timeout settings (15 minutes)
• Check interval (30 minutes)
• Container images used