kcl-lang/krm-kcl

Kubernetes Resource Model KCL Specification and Integrations including Kubectl, Kustomize, Helm, Helmfile, Crossplane, KPT, etc.

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓

kcl-lang/krm-kcl has 30+ stars and 10+ forks on GitHub, is written in KCL, and was last pushed on Oct 14, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on October 15th, 2026
Created on April 18th, 2023
Open Issues & Pull Requests: 2 (+0)
GitHub issues: Enabled
Number of forks: 18
Total Stargazers: 36 (+0)
Total Subscribers: 2 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 7.7 hours
Mean response time: 38.7 days
90th percentile: 77.0 days
Tracked items: 2

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (1)
  • help wanted (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

KRM KCL is a Kubernetes Resource Model function specification and interpreter that lets you write KCL code to generate, mutate, and validate Kubernetes resources.

The tool addresses the need to programmatically transform Kubernetes manifests using the KCL programming language. It works by accepting KCL scripts through a KCLRun functionConfig, executing them against input resources, and returning modified or validated output. The KCL source can come from local files, version control systems like GitHub, OCI registries, HTTP endpoints, or other sources. Within your scripts, you can read input resources and configuration via the options API, apply transformations like adding labels or injecting sidecars, validate resources against schemas, and return the modified resource list. The tool supports both declarative and imperative usage patterns.

You should consider this tool if you need to apply consistent transformations across Kubernetes manifests in a programmatic way. It suits projects where you want to enforce policies, generate resources from abstract models, or inject common configurations across many resources. The project integrates with multiple Kubernetes tooling ecosystems including Kubectl, Kustomize, Helm, Helmfile, KPT, Crossplane, and Flux, so adoption depends on which tools already exist in your workflow. If you are already using KCL elsewhere in your infrastructure, this provides a natural extension into Kubernetes resource management.

Development activity shows consistent engagement with the codebase through regular updates and refinements to both the core specification and integration points. The project maintains active examples and documentation that demonstrate practical usage patterns. Integration tests are present alongside unit tests, indicating attention to real-world deployment scenarios. The breadth of tool integrations suggests ongoing effort to make the project work within established Kubernetes ecosystems rather than requiring users to adopt entirely new workflows.