crossplane

Category: Ops & Delivery | Uploader: tikalk | Downloads: 0 | Version: v1.0（Latest）

Crossplane composition patterns for cloud-agnostic infrastructure as code. Use when writing Crossplane Compositions, XRDs (CompositeResourceDefinitions), or Claims, managing cloud resources declaratively from Kubernetes, or designing platform team infrastructure abstractions with Crossplane.

Changelog: Source: GitHub https://github.com/tikalk/agentic-sdlc-team-ai-directives

Directory Structure

Current level: skills/crossplane/

📄 SKILL.md 2.1 KB

SKILL.md

---
name: crossplane
description: "Crossplane composition patterns for cloud-agnostic infrastructure as code. Use when writing Crossplane Compositions, XRDs (CompositeResourceDefinitions), or Claims, managing cloud resources declaratively from Kubernetes, or designing platform team infrastructure abstractions with Crossplane."
---

# Crossplane Skill

## What This Skill Provides

Patterns for authoring Crossplane Compositions and XRDs that provide
developer-facing infrastructure abstractions backed by cloud provider
managed resources.

## When to Use This Skill

- Writing Crossplane Compositions or XRDs
- Creating developer-facing composite resource Claims
- Designing platform team infrastructure abstractions
- Migrating Terraform resource definitions to Crossplane
- Debugging Composition or Claim reconciliation issues

## Core Patterns

### XRD > Composition > Claim Hierarchy

**Rule**: Define a clear three-layer hierarchy for each infrastructure domain.

**Implementation**:
- **XRD**: Defines the API schema (the "CRD for platform users")
- **Composition**: Maps XRD fields to one or more cloud provider managed resources
- **Claim**: What application teams use to request infrastructure
- Keep XRDs stable; evolve Compositions without breaking Claim consumers

**References**: See @rule:devops/crossplane_compositions.md

### DRY Compositions with PatchSets

**Rule**: Avoid duplicating managed resource definitions across Compositions.

**Implementation**:
- Use `patchSets` for groups of patches applied to multiple resources
- Use `transforms` for value mapping rather than hardcoding environment-specific values
- Parameterize Compositions via XRD fields rather than forking per environment

**References**: See @rule:devops/crossplane_compositions.md

### Composition Validation and Testing

**Rule**: Validate Compositions before applying to production clusters.

**Implementation**:
- Use `crossplane beta validate` to lint XRDs and Compositions
- Test Claim rendering in an isolated dev cluster before promoting
- Monitor Composition health via `crossplane beta trace`

**References**: See @rule:devops/crossplane_compositions.md

Comments 0

Latest | Hot

Please login before commenting.

No comments yet. Be the first one!

crossplane

Directory Structure

SKILL.md

Report

Notice