https://www.gokure.dev/kure/dev/guides/index.htmlGuides Step-by-step guides for common Kure workflows. Using Kure as a Library - Import paths, creating resources, generating YAML Generating Flux Manifests - End-to-end cluster definition to disk Working with Generators - The GVK system and application generators Patching Resources - JSONPath patching and TOML patch format Building Kurel Packages - Creating reusable application packagesHugoen-ushttps://www.gokure.dev/kure/dev/guides/library-usage/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://www.gokure.dev/kure/dev/guides/library-usage/index.htmlUsing Kure as a Library Kure is primarily a Go library. This guide covers the basics of importing it, creating resources, and generating YAML output. Installation go get github.com/go-kure/kure Creating Resources Kure provides typed builder functions for Kubernetes and FluxCD resources. FluxCD Resources import "github.com/go-kure/kure/pkg/kubernetes/fluxcd" // Create a GitRepository source repo := fluxcd.GitRepository(&fluxcd.GitRepositoryConfig{ Name: "my-repo", Namespace: "flux-system", URL: "https://github.com/org/repo", Branch: "main", Interval: "5m", }) // Create a Kustomization that references the source ks := fluxcd.Kustomization(&fluxcd.KustomizationConfig{ Name: "my-app", Namespace: "flux-system", Path: "./clusters/production", Interval: "10m", Prune: true, SourceRef: kustv1.CrossNamespaceSourceReference{ Kind: "GitRepository", Name: "my-repo", }, }) See the FluxCD Builders reference for all available resource types.https://www.gokure.dev/kure/dev/guides/flux-workflow/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://www.gokure.dev/kure/dev/guides/flux-workflow/index.htmlGenerating Flux Manifests This guide walks through the complete workflow for generating a GitOps repository structure with Flux resources using Kure. Overview The workflow has four stages: Define the cluster topology using the domain model Select the Flux workflow engine Generate Flux resources and directory layout Write manifests to disk Step 1: Define the Cluster Use the fluent builder to define your cluster’s structure: import "github.com/go-kure/kure/pkg/stack" cluster := stack.NewClusterBuilder("production"). WithNode("infrastructure"). WithBundle("cert-manager"). WithApplication("cert-manager", certManagerConfig). End(). End(). WithNode("applications"). WithBundle("web-tier"). WithApplication("frontend", frontendConfig). WithApplication("api-gateway", apiConfig). End(). End(). Build() Each bundle becomes a Flux Kustomization, and each application generates its Kubernetes manifests.https://www.gokure.dev/kure/dev/guides/generators/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://www.gokure.dev/kure/dev/guides/generators/index.htmlWorking with Generators Generators provide a type-safe way to create application workloads from configuration. They implement the ApplicationConfig interface and are identified by GroupVersionKind (GVK) strings. Getting Started The fastest way to start a new project is with kure init: kure init my-cluster This creates a ready-to-use directory structure with cluster.yaml and an example application under apps/. You can then generate manifests with: kure generate cluster cluster.yaml See kure init --help for options like --gitops argocd.https://www.gokure.dev/kure/dev/guides/patching/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://www.gokure.dev/kure/dev/guides/patching/index.htmlPatching Resources Kure’s patch system lets you declaratively modify Kubernetes resources using JSONPath expressions. Patches are applied after resource generation, making them useful for environment-specific customization. When to Patch vs Configure Configure at generation time when you control the resource builder (set replicas, image, etc. in code) Patch after generation when you need to modify resources from external sources, or when the same base resources need different modifications per environment Patch File Formats TOML Format (.kpatch) The TOML format uses section headers to target resources:https://www.gokure.dev/kure/dev/guides/kurel-packages/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://www.gokure.dev/kure/dev/guides/kurel-packages/index.htmlBuilding Kurel Packages Kurel is the package system for creating reusable Kubernetes applications. A kurel package bundles base manifests, patches, and parameters into a self-contained unit that can be customized per deployment. Package Structure my-app.kurel/ ├── parameters.yaml # Variables and package metadata ├── resources/ # Base Kubernetes manifests │ ├── deployment.yaml │ ├── service.yaml │ └── namespace.yaml ├── patches/ # Modular customization patches │ ├── 00-base.kpatch # Global settings │ ├── features/ │ │ ├── 10-monitoring.kpatch │ │ └── 10-monitoring.yaml # Patch conditions │ └── profiles/ │ ├── 10-dev.kpatch │ └── 20-prod.kpatch └── README.md Creating a Package 1. Define Parameters # parameters.yaml kurel: name: my-application version: 1.0.0 description: "A sample application package" app: replicas: 3 image: repository: myapp tag: v1.0.0 monitoring: enabled: false 2. Add Base Resources Place standard Kubernetes manifests in resources/. These are the starting point before patches are applied.