Kubernetes Rendering
Kubernetes Rendering
Kubernetes Rendering turns Helm charts, reusable components, and templates into
plain Kubernetes manifests, from one configuration in Git. nyl render,
nyl diff, and nyl apply share one pipeline, so a local render and a CI
render of the same declaration take one path.
This is the first layer. It is the right place to start, and the right place to stop if Kubernetes is all you deploy. Kubernetes GitOps builds on it by publishing the rendered manifests to Git.
Concepts
Section titled “Concepts”Rendering Pipeline
The steps that render, diff, and apply share, from loading the project to filtering the final manifests.
Component System
Map Kubernetes-style resources to Helm charts with a predictable lookup model.
Git Integration
How Git-backed Helm charts and publication sources resolve through a shared local cache.
Workflow
Section titled “Workflow”CLI-First Workflows
Direct feedback from Nyl for bootstrapping, debugging, test clusters, and one-off operational checks.
Manifest validation
Run configured validators against the final Kubernetes manifests.
Kyverno Policies
Mutate and validate resources at render time, before they reach the cluster.
Renovate Integration
A reusable Renovate preset for Helm chart version bumps.