Custom Resource Definitions
Mission Control uses several Custom Resource Definitions (CRDs) to provide extended functionality in Kubernetes. These CRDs allow you to define various resources that Mission Control can manage, monitor, and interact with.
Available CRDs
| CRD | Kind | Description |
|---|---|---|
| Canary | Canary | Define health checks to monitor the availability of services |
| Component | Component | Define components for organizing and visualizing your infrastructure |
| Topology | Topology | Define relationships and hierarchies between components |
| Connection | Connection | Define connections to external systems and services |
| IncidentRule | IncidentRule | Define rules for incident detection and management |
| Notification | Notification | Define notification channels and rules |
| NotificationSilence | NotificationSilence | Define periods when notifications should be silenced |
| PermissionGroup | PermissionGroup | Define groups of permissions for RBAC |
| Permission | Permission | Define individual permissions for RBAC |
| Playbook | Playbook | Define automated workflows for operations |
| ScrapeConfig | ScrapeConfig | Define configurations for scraping metrics |
| ScrapePlugin | ScrapePlugin | Define plugins for scraping custom data sources |
Installation
These CRDs are automatically installed when you deploy Mission Control using the Helm chart. If you need to install them manually, you can use:
kubectl apply -f https://github.com/flanksource/mission-control-chart/tree/main/crd-chart/templates
Validation
Mission Control uses OpenAPI validation schemas to ensure that the resources you create are valid. You can find the full schemas in the duty repository.