/tags/dry-run/Recent content in Dry-Run on Layer5 DocumentationHugoen/kanvas/guides/deploying/dry-running-a-design/Mon, 01 Jan 0001 00:00:00 +0000/kanvas/guides/deploying/dry-running-a-design/<p>A dry run submits every component in the design to the Kubernetes API server of each target cluster as a server-side dry-run request. The API server validates the object exactly as it would on a real apply, including schema, field values, and admission, and then discards it. Nothing is created, updated, or persisted, so you can repeat a dry run as often as you like.</p> <h2 id="before-you-start" class="heading-link"> Before you start <a href="#before-you-start" class="heading-anchor" aria-label="Permalink to this heading">🔗</a> </h2> <ul> <li><strong>A connected cluster.</strong> Meshery must hold at least one connected Kubernetes context. With none, the request fails with error <code>meshery-server-1096</code>, Kubernetes cluster is unavailable.</li> <li><strong>A non-empty design.</strong> The Actions menu is disabled for an empty design.</li> <li><strong>Permission.</strong> Dry run is gated by the Validate Design permission. See <a href="/kanvas/reference/permissions/">Permissions by Role</a>.</li> <li><strong>A Meshery you run.</strong> The hosted kanvas.new site does not run dry runs.</li> </ul> <p>Meshery Server performs the dry run with the kubeconfig it holds. Meshery Operator, MeshSync, and the broker are not required.</p>