Kubernetes GitOps
Kubernetes GitOps
Kubernetes GitOps publishes rendered manifests to Git for a reconciler to sync. Nyl compiles each deployment target into an ordinary directory of Kubernetes manifests in a Git revision, with Argo CD Applications and least-privilege AppProjects. Argo CD, Flux, or another reconciler syncs the published YAML, and Nyl never runs in the cluster’s reconciliation path.
This layer builds on Kubernetes Rendering: the same configuration renders the manifests, so what you inspect locally is what CI publishes.
Start here
Section titled “Start here”Concepts
Section titled “Concepts”Project Structure and Discovery
Resources are discovered project-wide, from the directory containing nyl.toml and beneath it.
Targets and Cluster Variation
A Cluster models one destination; a DeploymentTarget binds it to deployment intent and publication coordinates.
Release Inputs
Typed inputs that each DeploymentTarget binds, for values that differ per environment.
Rendered Layout
The tree Nyl writes into a target's publication prefix.
Trust and Admission Boundaries
What Nyl validates and records, and why it is not the ultimate admission boundary.
Workflow
Section titled “Workflow”Render and Validate
Render a DeploymentTarget into a checkout of its publication repository.
Diff in Pull Requests
Compare the desired tree with the currently published deployment revision.
Publish
Publish from the protected branch.
Move a Publication
What happens when a target's repository, revision, or path prefix changes.