ksm-crossplane-adapter

Adapt kube-state-metrics configurations to monitor Crossplane resources.

4|1|Updated Jan 17, 2026

Search Tags:#monitoring #metrics #Prometheus #ksm #Crossplane #kube-state-metrics #Crossplane resources

Ready to run

npx skills add https://github.com/kingdon/skills --skill ksm-crossplane-adapter

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ksm-crossplane-adapter
Source: https://github.com/kingdon/skills/tree/main/.github/skills/ksm-crossplane-adapter
Command: npx skills add https://github.com/kingdon/skills --skill ksm-crossplane-adapter

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires kubectl, curl, jq, sha256sum, and includes scripts (resource) components.

What problem does it solve?

This Skill adapts kube-state-metrics configurations to monitor Crossplane resources beyond standard KStatus patterns.

Core Features & Use Cases

Crossplane-aware metrics: generate and monitor KSM config for Synced and Ready conditions across Crossplane resources.
Slash command driven validation: activate with /ksm-crossplane to run the end-to-end monitoring workflow.
Prometheus compatibility: ensures metrics surface in Prometheus and supports alerting for Crossplane resources.

Quick Start

Activate via /ksm-crossplane, then run the validation script: bash .github/skills/ksm-crossplane-adapter/scripts/validate.sh

Frequently Asked Questions about ksm-crossplane-adapter

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I monitor Crossplane resource conditions in Prometheus using kube-state-metrics?▼

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.

What is the best way to collect metrics for Crossplane Managed Resources beyond standard KStatus patterns?▼

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.

Do I need kubectl and jq to validate kube-state-metrics configurations for Crossplane?▼

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.

Can I set up alerting for Crossplane Synced and Ready states in my existing Prometheus setup?▼

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.

How do I validate that my Crossplane kube-state-metrics adapter is collecting metrics correctly?▼

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.

What are the limitations of using standard kube-state-metrics for Crossplane environments?▼

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.