ksm-crossplane-adapter

You can monitor Crossplane resources by applying custom kube-state-metrics configurations that track Synced and Ready conditions across Providers and Managed Resources, making them available as Prometheus metrics for alerting.

Collecting Crossplane metrics beyond standard KStatus requires adapting kube-state-metrics templates to specifically target and surface the Synced and Ready conditions of your Compositions and Managed Resources.

Yes, validating Crossplane metric collection requires kubectl, jq, and curl dependencies to execute the end-to-end monitoring workflow script and verify connectivity against your environment.

Yes, this approach ensures metrics for Crossplane Synced and Ready conditions are surfaced in Prometheus, allowing you to configure standard alerting rules for your Providers and Managed Resources.

You can validate metric collection by activating the slash command workflow and running the provided validation script to test end-to-end connectivity and ensure Crossplane metrics are properly generated.

Standard kube-state-metrics lacks awareness of Crossplane-specific resource structures, failing to track Synced and Ready conditions across Providers and Compositions without adapted configuration templates.