# Flux Introduces Schema Validation Plugin and Ecosystem Schema Catalog

DevFeed: [Flux Introduces Schema Validation Plugin and Ecosystem Schema Catalog](<https://devfeed.tech/articles/blog-introducing-flux-schema-and-the-ecosystem-catalog-48653.md>)

Original publisher: [Read original article](<https://fluxcd.io/blog/2026/07/flux-schema-validation/>)

Author: Stefan Prodan

Published: 2026-07-13T12:00:00Z

Content type: release

Language: en

Sources: [Flux - Blog](<https://devfeed.tech/sources/flux-blog.md>)

Topics: [flux](<https://devfeed.tech/topics/flux.md>), [JSON Schema](<https://devfeed.tech/topics/json-schema.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [GitOps](<https://devfeed.tech/topics/gitops.md>), [ci](<https://devfeed.tech/topics/ci.md>), [Model Context Protocol](<https://devfeed.tech/topics/model-context-protocol.md>), [servers](<https://devfeed.tech/topics/servers.md>)

Tags: [ci](<https://devfeed.tech/tags/ci.md>), [flux](<https://devfeed.tech/tags/flux.md>), [gitops](<https://devfeed.tech/tags/gitops.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [schema](<https://devfeed.tech/tags/schema.md>), [schemas](<https://devfeed.tech/tags/schemas.md>), [server](<https://devfeed.tech/tags/server.md>)

## AI overview

Flux introduces a CLI plugin that validates Kubernetes manifests against JSON Schema and CEL rules using the same evaluation semantics as the Kubernetes API server. It also announces a hosted catalog of schemas and LLM-optimized indexes for Cloud Native projects, available to CI pipelines over a CDN and to AI agents over MCP.

## Source excerpt

In this blog post, we introduce Flux Schema, a new Flux CLI plugin for validating Kubernetes manifests against JSON Schema and CEL rules using the same evaluation semantics as the Kubernetes API server. Alongside the plugin, we're announcing the Ecosystem Schema Catalog, a hosted catalog of JSON Schemas and LLM-optimized indexes covering the Kuberentes ecosystem of controllers, served to CI pipelines over CDN and to AI agents over MCP. Why Another Validation Tool The GitOps workflow has a well-known blind spot: a manifest with a typo, a wrong type, or a violated CEL rule sails through git push and only fails when Flux applies it on the cluster. By then the error lives in your main branch and shows up as a failed reconciliation instead of a failed pull request. Tools like kubeconform (which inspired this project) solved part of the problem by validating manifests against JSON Schemas offline. Flux Schema builds on that idea and extends it with the API server's own evaluation semantics: Strict schema validation: every field of every Kubernetes built-in kind and custom resource is checked. Unknown fields, wrong types, and missing required properties are reported as schema violations. CEL evaluation: the x-kubernetes-validations rules embedded in CRDs are evaluated with the same engine as the Kubernetes API server. A HelmRelease missing both chart and chartRef is caught locally, not on the cluster. Strict YAML decoding: duplicate keys are rejected, matching Flux behavior, and metadata names, namespaces, labels, and annotations are checked against API server rules (DNS-1123, qualified names). Ecosystem catalog: the ecosystem schema location resolves to schemas.fluxoperator.dev, a CDN-hosted catalog for over a hundred Cloud Native projects, extracted from upstream releases and rebuilt daily. SOPS-aware: the SOPS metadata fields can be stripped before validation, so encrypted Secrets are checked without decryption. Getting Started Install the plugin with the Flux CLI: flux