Skip to main content

flux-topology

skills.sh

A CLI + agent skill that builds a dependency and topology graph of a Kubernetes/FluxCD GitOps repository by static analysis, so AI agents can reason about service relationships without cluster access.

Install

pip install flux-topology

Optional — install the agent skill from skills.sh:

npx skills add seppaleinen/flux-topology-mcp

No MCP server is required. Run the CLI from your GitOps repo root; it reads from flux/ in the working directory.

Subcommands

Command Description
build [dir] [--force] Build the topology cache (.fluxtop/)
map [dir] [--json] Top-level view: domains, hub apps by edge count, warnings
trace <app> [dir] [--direction out|in|both] [--depth N] [--json] BFS blast radius from any app with typed edges
find-refs <pattern> [dir] [--json] Regex search for references across all apps
app-card <app> [dir] [--json] Full card for one app: workloads, services, edges
check-freshness [dir] [--json] Check if the topology cache is up to date (never rebuilds)

[dir] defaults to .. A directory is resolved to its flux/ subdirectory when present; otherwise the directory itself is treated as the flux root.

Exit codes

Code Meaning
0 Found / fresh
1 Stale, corrupt, not-found, or invalid input
2 Usage error (argparse)
3 No cache (check-freshness only)

CLI examples

# Build the topology cache (.fluxtop/)
flux-topology build

# Rebuild even when the cache is fresh
flux-topology build --force

# Human-readable overview
flux-topology map

# Machine-readable output
flux-topology map --json

# Blast radius: what depends on this app? (depth 5)
flux-topology trace apps/backend --direction in

# Find every app referencing a shared resource
flux-topology find-refs "postgres-rw\.postgres\.svc\."

# Full card for one app
flux-topology app-card apps/radarr

# Freshness check (exit codes 0/1/3)
flux-topology check-freshness

How it works

  1. Discovers apps by walking flux/ and finding ownership signals (HelmReleases, Kustomizations, Deployments, Services)
  2. Extracts workloads, services, ingress hosts, and refs per app
  3. Resolves edges between apps from cross-references
  4. Caches everything in .fluxtop/ — rebuilt only when source files change

Hybrid freshness

The cache is checked against a fingerprint of all YAML files on every query:

  • No cache — map/trace/find-refs/app-card auto-build once and then answer normally. check-freshness instead reports NO CACHE (exit 3) and never rebuilds.
  • Fresh — the cache matches the working tree; queries answer from it.
  • Stale / corrupt — queries surface a notice and exit 1 without rebuilding, so results are never silently outdated. Rebuild explicitly with flux-topology build --force, or just build (which also rebuilds when the fingerprint no longer matches).

Deployment note (dotfiles env)

The always-on flux-topology MCP server was removed from the shared MCP list in the user's dotfiles environment (Stow-managed). The tool is now used on-demand via the CLI + skill. Re-push the rewritten skill via skills.sh.

Development

git clone https://github.com/seppaleinen/flux-topology-mcp.git
cd flux-topology-mcp
pip install -e ".[dev]"
pytest

License

MIT

Release files for flux-topology 0.3.4

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for flux-topology 0.3.4
File Size Uploaded
flux_topology-0.3.4.tar.gz 46.3 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for flux-topology 0.3.4
File Interpreter ABI Platform
flux_topology-0.3.4-py3-none-any.whl Python 3 none any Details

Total release size: 71.9 kB

Release files / flux_topology-0.3.4.tar.gz

Download URL flux_topology-0.3.4.tar.gz
Size 46.3 kB
Tags Source
SHA-256 checksum
How to use checksums
d8ffbb78bf82433b8b345063c4fd2775436b3066714f167ecd44e2b23ac58bcf
BLAKE2b-256 checksum
How to use checksums
ce5632e142907ebc47befb09f8738abc36ba52f1a99c39f00595edc6938d091e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 25, 2026.

Transparency log

Release files / flux_topology-0.3.4-py3-none-any.whl

Download URL flux_topology-0.3.4-py3-none-any.whl
Size 25.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
21d44b3e9e9c46771ba7c9b6adacdc702b02a0729eb5015e06eac84d33fd9600
BLAKE2b-256 checksum
How to use checksums
0a332e2a71dfe6f7c8241fba142188052e9a4d8ac266f257fe317144568021e2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 25, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.3.4 This release

2 release files

0.3.3

2 release files

0.3.2

2 release files

0.3.1

2 release files

0.2.4

2 release files

0.2.2

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page