How rverchere/ovh-mks-exporter works
Main Components
a. External Systems:
• OVH Cloud API (primary data source)
• Prometheus Server (metrics consumer)
• Kubernetes Cluster (deployment environment)
b. Internal Components:
• OVH MKS Exporter (core application)
• Metrics Collectors (internal modules)
• HTTP Server (for exposing metrics)
Component Relationships
• OVH MKS Exporter → OVH Cloud API (API calls with authentication)
• Prometheus → OVH MKS Exporter (scrapes metrics)
• Kubernetes → OVH MKS Exporter (hosts the application)
Detailed Component Breakdown
a. OVH MKS Exporter Core (based on internal/ directory):
• Collector Module (collector.go)
• Exporter Module (exporter.go)
• OVH Metrics Module (ovh_metrics.go)
• Version Module (version.go)
b. Configuration Layer:
• Environment Variables
• Kubernetes Secrets (for OVH API credentials)
• Helm Chart Configuration
Key Workflows to Highlight
a. Metric Collection Flow:
1. Prometheus triggers scrape
2. Exporter calls OVH API
3. Data is transformed into metrics
4. Metrics are exposed via HTTP endpoint
b. Deployment Flow:
1. Helm chart deployment
2. Secret management
3. ServiceMonitor configuration
Additional Details
Specific elements:
• Metric types (as listed in README)
• Authentication flow with OVH API
• Kubernetes resources (ServiceMonitor, Service, Deployment)
Architectural Notes
Aspects:
• Prometheus integration pattern
• Kubernetes-native design
• Secure credential management
• Modular collector design
This design should reflect the project's nature as a Kubernetes-native Prometheus exporter while highlighting its specific role in monitoring OVH managed Kubernetes clusters.