Validate a Design

Mon, 01 Jan 0001 00:00:00 +0000

Validation checks the configuration of each component in a design against the schema of that component’s definition. It runs in your browser, needs no cluster, and changes nothing. Run it while you build to catch missing or malformed fields before a dry run or a deployment spends time on them.

Before you start 🔗

Environment. Validation runs in a Meshery you run. The hosted kanvas.new site does not run it and shows a self-hosted-feature prompt instead.
A non-empty design. The Actions menu is disabled while the design has no components. An unsaved design validates; Kanvas validates the design as it is on the canvas.
Permission. On mobile, the Validate Design permission gates the action. See Permissions by Role.

What validation checks 🔗

Checked	Not checked
Each component’s configuration against the JSON schema of its registered definition, with all errors collected per component	Relationships between components
Required fields, types, and formats, including 32-bit and 64-bit integers and integer-or-string values	Dependencies, namespaces, and cross-references
	Anything in the target cluster

Annotation components (text, shapes, and other visual elements) carry no infrastructure and are skipped. They are counted separately in the summary.

Component Badges

Mon, 01 Jan 0001 00:00:00 +0000

A badge is a small marker Kanvas draws on the edge of a component to report something about it: errors waiting to be fixed, components held inside it, a link, or where it came from. Badges are status, not decoration. A count on a badge tells you there is something to read, and clicking it shows what.

Which badges appear depends on the mode. Designer mode draws badges that help you build a valid design. Operator mode draws badges about live resources.

Validation on Layer5 Documentation

Validate a Design

Before you start 🔗

What validation checks 🔗

Component Badges