Configuring Components
Categories:
A component is the fundamental building block of a design - it represents one piece of the infrastructure under management, and its configuration is what will actually be applied when the design is deployed. The component configurator is where that configuration is edited.
Kanvas does not ask you to write YAML for this. The form is built from the component’s own definition, as published by the model it belongs to, so the fields you see are exactly the fields that component supports, in the version of the model you have selected.
Opening the configurator π
With a component on the canvas:
- Double-click the component, or
- Right-click it and choose Configure.
The configurator opens in a panel beside the canvas. The component stays selected while it is open, so you can see what you are editing.
The header π
| Control | What it does |
|---|---|
| Component icon | Hovering shows the model version the component is using. |
| Version menu | Appears when the model has more than one version available. Switching versions rebuilds the form against that version’s definition. |
| Search | Filters the form down to matching fields. On a component with many fields this is far quicker than scrolling; if nothing matches, the form says so rather than appearing empty. |
| Help | Shows the component’s own description, as published by its model. |
| Expand / collapse | Maximizes the configurator to fill the workspace, and restores it. |
| Delete | Removes the component from the design. |
Tabs π
The configurator is organized into tabs. Which are present depends on the component and on your permissions:
- Config - the component’s specification. This is where the substantive configuration is done.
- Labels - Kubernetes labels and annotations for the component, edited separately from the rest of the spec so that metadata does not crowd out configuration.
- Json Schema - the raw schema the form was generated from, in a JSON viewer. Useful when you want to see exactly what a field expects, and it links out to the component’s entry in the Meshery registry.
- Relationships - the relationships this component participates in, and the components at the other end of them.
Field help and validation π
Each field carries its documentation with it. A ? icon at the right of a field opens a tooltip containing that field’s description, taken straight from the component’s definition - so the guidance you get is the upstream project’s own, not a Kanvas paraphrase. Nested objects and arrays carry the same help on their group headings.
When a value is not valid for that field, a red error icon appears alongside, and its tooltip gives the validation message. The component itself also picks up a validation warning badge on the canvas, so a problem you scroll past in the form is still visible when you close the panel. See Interpreting Component Badges.
Changes take effect as you type π
There is no Apply button. Edits are written into the design shortly after you stop typing, the canvas updates to match, and the design is saved to your account - see Saving Designs. Undo reverses a configuration change like any other edit.
See Also π
- Understanding Design Components: What the components on the palette represent.
- Understanding Tool Modes: Every mouse interaction available on the canvas, including the ones that open this panel.
Related Reading
- Canvas Actions
- Cloning a Design
- Creating Relationships
- Deleting a Design
- Deploying Designs
- Dry Running a Design
Recent Discussions on Kanvas
- Jul 12 | Unleash Visual Power: Import Your Configs by zihan kuang
- Oct 14 | Explore Meshery's Published Relationship Design Examples by Awani Alero
- Oct 03 | Design Review RFC: Kanvas Empty State Enhancement by Lee Calcote
- Jul 19 | [For Discussion] Visual indication of semantically vs non-semantically meaningful Meshery components by Lee Calcote
- Jun 07 | What are the conditions for a "System is unhealthy" warning? by James
- May 30 | Looking for a meshmate to help with first PR by Faisal Imtiyaz123
- Feb 28 | For Discussion: Capturing potential, but unrealized Relationships in Design Snapshots by Lee Calcote
- Feb 12 | Hint on Scaling & Verifying Cronjob in Playground by Sandra Ashipala




