Skip to content
J·BJon BishopFractional growth marketer

Developer tools · llms.txt file breakdown

ControlPlane llms.txt

A directly retrieved Markdown index for ControlPlane's documentation, with 41 links across 5 detected headings.

The actual file

Source Markdown

The saved llms.txt text, displayed as source. The file belongs to its publisher; the live endpoint may change.

Open saved text ↗

Complete saved Markdown shown below.

# Flux CD Enterprise by ControlPlane

ControlPlane offers a hardened, enterprise-grade distribution for the CNCF-graduated Flux project including 24/7 support, security patches, and expert guidance for production deployments.
The enterprise distribution bundles the Flux Operator and the Flux MCP Server, which are designed to automate the management of Flux controllers at-scale and provide AI-assisted GitOps capabilities.

## Flux Operator Overview

Flux Operator offers a production-ready solution for managing the delivery of application and infrastructure workloads on multi-tenant Kubernetes clusters using GitOps principles.
The operator is designed to automate the installation, configuration, and upgrade of the Flux controllers as well as to provide advanced features such as preview environments for testing pull requests, deployment windows, and self-service capabilities for developers.
The Flux Operator is an open-source project licensed under AGPL-3.0 and is developed by the CNCF Flux core maintainers part of the ControlPlane team.

## Flux Operator Documentation

- Installation
    - [Flux operator installation](https://fluxoperator.dev/docs/guides/install.md)
    - [Migration of bootstrapped clusters](https://fluxoperator.dev/docs/guides/migration.md)
- Flux Instance Configuration
    - [Flux controllers configuration](https://fluxoperator.dev/docs/instance/controllers.md)
    - [Flux instance customization](https://fluxoperator.dev/docs/instance/customization.md)
    - [Cluster sync configuration](https://fluxoperator.dev/docs/instance/sync.md)
    - [Flux controllers sharding](https://fluxoperator.dev/docs/instance/sharding.md)
    - [Flux monitoring and reporting](https://fluxoperator.dev/docs/instance/monitoring.md)
- Application Definitions and Self-Service Environments
    - [Using ResourceSets for Application Definitions](https://fluxoperator.dev/docs/resourcesets/app-definition.md)
    - [Using ResourceSets for Time-Based Delivery and Deployment Windows](https://fluxoperator.dev/docs/resourcesets/time-based-delivery.md)
    - [Using ResourceSets for Image Update Automation](https://fluxoperator.dev/docs/resourcesets/image-automation.md)
    - [Ephemeral Environments for GitHub Pull Requests](https://fluxoperator.dev/docs/resourcesets/github-pull-requests.md)
    - [Ephemeral Environments for GitLab Merge Requests](https://fluxoperator.dev/docs/resourcesets/gitlab-merge-requests.md)
- API References
    - [FluxInstance CRD](https://fluxoperator.dev/docs/crd/fluxinstance.md)
    - [FluxReport CRD](https://fluxoperator.dev/docs/crd/fluxreport.md)
    - [ResourceSet CRD](https://fluxoperator.dev/docs/crd/resourceset.md)
    - [ResourceSetInputProvider CRD](https://fluxoperator.dev/docs/crd/resourcesetinputprovider.md)

## Flux Web UI

The Flux Web UI (also known as Flux Status Page) provides a real-time dashboard for monitoring GitOps pipelines and cluster state.
It offers visibility into Flux resources, their reconciliation status, and events, helping teams quickly identify and troubleshoot deployment issues.
The Web UI supports Single Sign-On (SSO) with various identity providers and role-based access control for secure multi-user access.
The Flux Web UI is a subproject of the Flux Operator licensed under AGPL-3.0.

### Flux Web UI Documentation

- [Standalone installation](https://fluxoperator.dev/docs/web-ui/standalone-install.md)
- [Ingress configuration](https://fluxoperator.dev/docs/web-ui/ingress.md)
- [User management](https://fluxoperator.dev/docs/web-ui/user-management.md)
- [SSO with Dex](https://fluxoperator.dev/docs/web-ui/sso-dex.md)
- [SSO with Keycloak](https://fluxoperator.dev/docs/web-ui/sso-keycloak.md)
- [SSO with OpenShift](https://fluxoperator.dev/docs/web-ui/sso-openshift.md)
- [SSO with Microsoft Entra](https://fluxoperator.dev/docs/web-ui/sso-microsoft.md)
- [Config API reference](https://fluxoperator.dev/docs/web-ui/web-config-api.md)

## Flux MCP Server

The Flux Model Context Protocol (MCP) Server connects AI assistants directly to your Kubernetes clusters running Flux Operator, enabling seamless interaction through natural language.
It serves as a bridge between AI tools and your GitOps pipelines, allowing you to analyze the cluster state, troubleshoot deployment issues, and perform operations using conversational prompts.
The MCP Server is a subproject of the Flux Operator licensed under AGPL-3.0.

### Flux MCP Server Documentation

- [Flux MCP Server Installation](https://fluxoperator.dev/docs/mcp/install.md)
- [Flux MCP Server Prompting Guide](https://fluxoperator.dev/docs/mcp/prompting.md)
- [Flux MCP Server Tools](https://fluxoperator.dev/docs/mcp/tools.md)

## CNCF Flux CD

Flux is a leading GitOps Continuous Delivery tool used to streamline and automate application deployments on Kubernetes.
Flux enables teams to achieve a reliable and auditable delivery process while promoting collaboration and traceability across different environments.
Flux is powered by the GitOps Toolkit, a set of composable APIs and specialized tools that enable a wide range of continuous delivery use-cases, from simple Kubernetes deployment pipelines to multi-tenant and multi-cluster progressive delivery rollouts.
Flux is a Cloud Native Computing Foundation (CNCF) graduated project, licensed under the Apache License 2.0.

### Flux API Documentation

- [GitRepository CRD](https://fluxoperator.dev/docs/crd/gitrepository.md)
- [OCIRepository CRD](https://fluxoperator.dev/docs/crd/ocirepository.md)
- [Bucket CRD](https://fluxoperator.dev/docs/crd/bucket.md)
- [Kustomization CRD](https://fluxoperator.dev/docs/crd/kustomization.md)
- [HelmRelease CRD](https://fluxoperator.dev/docs/crd/helmrelease.md)
- [Webhook Receiver CRD](https://fluxoperator.dev/docs/crd/receiver.md)
- [Alert Provider CRD](https://fluxoperator.dev/docs/crd/provider.md)
- [Alert CRD](https://fluxoperator.dev/docs/crd/alert.md)
- [ImageRepository CRD](https://fluxoperator.dev/docs/crd/imagerepository.md)
- [ImagePolicy CRD](https://fluxoperator.dev/docs/crd/imagepolicy.md)
- [ImageUpdateAutomation CRD](https://fluxoperator.dev/docs/crd/imageupdateautomation.md)
- [ArtifactGenerator CRD](https://fluxoperator.dev/docs/crd/artifactgenerator.md)

## About ControlPlane Group Limited

ControlPlane is a cybersecurity consultancy firm based in London, New York, and Auckland with a focus on Kubernetes supply chain security, MLOps, and AI.
ControlPlane is the main sponsor of the Flux CD project and employs core maintainers who contribute full-time to CNCF Flux and its ecosystem.

For more information about ControlPlane, visit [control-plane.io](https://control-plane.io).

For more information about the ControlPlane Enterprise for Flux CD offering, visit [fluxcd.control-plane.io](https://fluxcd.control-plane.io/).

Measured from the saved file

Linked document

UTF-8 text size
6.7 KB6814 bytes
Token count
1465o200k_base encoding
Markdown links
4141 distinct URLs
Fenced code blocks
094 lines in the file

Size measures the captured UTF-8 text, not compressed transfer size. Tokens are counted with a named tokenizer; other models can count differently. Neither measure establishes context compatibility or answer quality.

Project H1
Flux CD Enterprise by ControlPlane

Context architecture

How the content is divided

6 H2 sections organize 41 parsed Markdown links. 39 links point to .md or .markdown paths; 40 link occurrences use another hostname. Linked destinations have not been recursively validated.

H2 sectionLinksUTF-8 bytesTokens
Flux Operator OverviewLine 60600105
Flux Operator DocumentationLine 12161695378
Flux Web UILine 3581151265
Flux MCP ServerLine 533726147
CNCF Flux CDLine 65121537357
About ControlPlane Group LimitedLine 872536110

Link counts exclude parsed fenced and inline code and resolve relative destinations against the final endpoint. Section sizes cover the text below each H2 until the next H2.

Embedded material

Code, installation and API examples

Fenced blocks
0 closed
Declared languages
No fenced blocks detected
Package-install commands
0 detected in fenced or inline code
Authentication examples
0 fenced lines match API-key, Authorization, Bearer, OAuth or access-token patterns
HTTP request examples
0 fenced lines match request-method patterns
Authentication links
0 links have authentication-related labels

Embedded example text and links to further documentation are counted separately. A code block does not establish that a sample runs or that an authentication flow succeeds.

Publisher prioritization

The Optional section

No H2 section named “Optional” was detected in this file.

The community proposal uses Optional by convention for secondary links that can be skipped for a shorter context. This label does not establish that everything outside it is critical, or that the material inside it is deprecated.

Machine-readable routes

MCP references and configuration text

MCP-related text was detected in the captured file. 3 links have MCP-related labels or paths. 0 fenced lines match mcpServers, mcp_servers or an mcp add command.

These are text and link observations. No MCP server connection, authentication or tool call was tested.

Index and bundle

llms-full.txt companion

Not found at checked URLs

A verified text response establishes a companion at the checked URL. It does not prove the bundle contains all product documentation, that generation is automated, or that it fits an assistant’s context window.

Change evidence

What can be said about freshness

This capture establishes a baseline. Update frequency cannot be determined from one observation.

Linked release and migration material

2 links have release, changelog, deprecation or migration terms in their labels or paths. These provide places to investigate product changes separately.

File changes can reveal documentation edits or navigation changes. They do not by themselves measure product release velocity, accuracy, agent adoption or AI visibility.

Capture identity and measurement method
Requested endpoint
https://fluxcd.control-plane.io/llms.txt
Final endpoint
https://fluxcd.control-plane.io/llms.txt
HTTP status
200
Content type
text/plain; charset=utf-8
Text retrieval
Firecrawl literal text capture
Tokenizer
tiktoken 0.14.0 · o200k_base
SHA-256 of saved UTF-8 text
67654e2768eb0392114f0ff511fadb000ed612245472435ee1677782467cc9f2

Counts use a deterministic parser, not a spec-compliance grade. Unusual Markdown and indented code can fall outside its recognized patterns. See the llms.txt proposal and tokenizer implementation.

Related tools and resources

Contact Jon