You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The `kalco validate` command is a high-level wrapper designed specifically for **CI/CD Pipelines**. It automates the entire drift detection workflow for Pulse/Merge Requests.
11
+
12
+
## Overview
13
+
14
+
Unlike `kalco diff`, which compares a single file, `kalco validate`:
15
+
1.**Auto-Detects Changes**: Finds which manifests changed between your current branch and the base branch (e.g., `origin/master`).
16
+
2.**Fetches Base Content**: Automatically retrieves the "before" state of files from git to enable [Smart Drift Detection]({{ site.baseurl }}/commands/diff#smart-drift-detection---ignore-base).
17
+
3.**Generates Report**: Produces a consolidated Markdown report of all validations.
18
+
4.**Ignores Defaults**: Automatically enables `--ignore-extra-fields` to reduce noise.
19
+
20
+
## Syntax
21
+
22
+
```bash
23
+
kalco validate [flags]
24
+
```
25
+
26
+
## Flags
27
+
28
+
| Flag | Description | Default | Required |
29
+
|------|-------------|---------|----------|
30
+
|`--base`| Base branch/ref to compare against |`origin/master`| No |
Copy file name to clipboardExpand all lines: docs/index.md
+27-13Lines changed: 27 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,13 +8,23 @@ nav_order: 1
8
8
9
9
Welcome to the official documentation for **Kalco** (Kubernetes Analysis & Lifecycle Control).
10
10
11
-
Kalco is the CLI tool that bridges the gap between your Git configuration and your actual Kubernetes cluster state.
11
+
Kalco is a powerful CLI tool designed to bridge the gap between your Git configuration (Intent) and your running Kubernetes cluster (Reality). It provides a robust workflow for **Snapshotting**, **Diffing**, and **Validating** cluster state.
12
12
13
13
## 🌟 Why Kalco?
14
14
15
-
-**Backup & Audit**: Snapshot your entire cluster to Git-friendly YAML.
16
-
-**GitOps Validation**: Detect "drift" between what you *think* is deployed (Git) and what *is* deployed (Cluster).
17
-
-**Environment Management**: Switch context configurations easily between Prod, Staging, and Dev.
15
+
In complex Kubernetes environments, "Drift" is inevitable. Someone patches a deployment manually, a controller adds default fields, or a Helm chart renders differently than expected. Kalco solves this by:
16
+
17
+
-**📸 Snapshotting**: Exporting your entire cluster state into clean, Git-friendly YAML files.
18
+
-**🔍 Diffing**: performing "Smart Diffs" that ignore noise (like timestamps, `managedFields`, and dynamic status) to show only *real* changes.
19
+
-**🛡️ Validating**: Integrating into CI/CD pipelines to prevent drift *before* it merges.
20
+
21
+
## 🏗️ How It Works
22
+
23
+
Kalco operates on a simple but powerful loop:
24
+
25
+
1.**Export**: `kalco export` connects to your cluster and downloads resources, stripping away runtime noise to create a "Golden Snapshot".
26
+
2.**Compare**: `kalco diff` compares your local manifests (or Helm charts) against this snapshot.
27
+
3.**Validate**: `kalco validate` automates this process in CI, fetching the base branch, detecting changed files, and verifying that your PR matches the cluster state (or intended changes).
-**[GitOps Validation Pipeline]({{ site.baseurl }}/tutorials/gitops-validation)**: A complete walkthrough of setting up a Drift Detection Pipeline for raw manifests using GitHub Actions and ArgoCD.
0 commit comments