Integrations Overview#
Reloader integrates with a wide range of Kubernetes-native tools for secrets management, certificate automation, and configuration delivery.
This section provides an overview of:
- How integrations work with Reloader
- The different support and validation levels
- Which integrations are validated and supported in Reloader Enterprise
- What community users can expect
Each integration has its own dedicated section with architecture notes, step-by-step examples, and operational considerations.
All integrations work with both Reloader OSS and Reloader Enterprise. Enterprise customers receive commercial support and SLA coverage.
How integrations work with Reloader#
Reloader itself is tool-agnostic.
It watches Kubernetes resources such as:
SecretsConfigMaps
When these change, Reloader can trigger safe rollouts of supported workloads (e.g. Deployments, StatefulSets, Rollouts), regardless of how those resources were created or updated.
Integrations typically follow this flow:
External system
↓
Kubernetes Secret / ConfigMap
↓
Reloader detects change
↓
Controlled workload rollout
Because the integration point is Kubernetes-native, many tools can work with Reloader. The difference lies in validation, guarantees, and support.