Import and Merge Designs
Bring Kubernetes manifests, Helm charts, Docker Compose files, Kustomize projects, and Meshery designs into Kanvas, and merge one design into another.
A design is a single record in Layer5 Cloud. It has one owner, lives in one workspace, and carries a visibility (private, public, or published) and a version. These guides cover each way a design enters, changes state, and leaves that record.
Two defaults shape everything below. A design saved for the first time is public, whatever visibility the client requests. Every save of an existing design raises its patch version by one (0.0.1, 0.0.2, and so on).
| Goal | Guide |
|---|---|
| Bring in a manifest, Helm chart, Compose file, Kustomize project, or design, or merge one design into another | Import and Merge Designs |
| Understand autosave, the save indicator, Save as, and plan limits | Save Designs |
| Start from a public or published design | Clone a Design |
| Back up a design or hand it to other tools | Export Designs |
| Show a design on another site | Embed Designs |
| Make a design available in the catalog | Publish Designs |
| Remove a design permanently | Delete a Design |
For the exact formats Kanvas accepts and produces, see Supported Import and Export Formats. To share a design with specific people, see Share Designs.
Every new design lands in exactly one workspace: the workspace you have selected for the current organization, or the first workspace you can see in that organization. If the organization has no workspace, saving, importing, and cloning fail. Creating a design is refused while the organization selector is set to all.
Anonymous users on kanvas.new can create, save, and import designs. Those designs move to the account when the user signs in. Sharing and publishing require an account.
Bring Kubernetes manifests, Helm charts, Docker Compose files, Kustomize projects, and Meshery designs into Kanvas, and merge one design into another.
How Kanvas saves a design automatically, what the save indicator reports, how to save a copy, and what happens when a save fails.
Copy a public or published design into your own workspace to use as a template, and learn what carries over.
Export a design as a design file, an OCI image, a Kubernetes manifest, a Helm chart, or an embeddable script, and know what each format keeps.
Show a design on a web page, blog, or documentation site with an exported JavaScript snapshot, including WordPress, React, and Hugo.
Publish a design to the Layer5 Cloud catalog, understand request and approval states, unpublish it, and ship it to Artifact Hub yourself.
Permanently delete a design you own, and understand what deletion does and does not affect.