Deploying Designs

Each Meshery design is deployable to one or more Kubernetes clusters.

Deployment Errors 🔗

Missing Namespace: This error occurs when you attempt to create a Kubernetes resource without specifying a namespace. Kubernetes requires that all resources have an associated namespace.

Empty Label Selector: This error indicates an empty label selector.

Troubleshooting Errors 🔗

When reviewing validation, dry run, or deployment issues, you’ll notice specific error codes denoted from time to time.

As a system, Meshery itemizes different errors that occur and assigns a unique error code to each along with details on how to remediate the issue at hand.

For the comprehensive list of error codes refer to Error Code Reference in the Meshery documentation.

If you encounter persistent issues consider consulting the Meshery Community forum

Using the Notification Center for Troubleshooting 🔗

The Notification Center in Meshery helps manage events during the deployment process. It provides real-time updates and alerts on the status of the deployment. This feature can be particularly useful for troubleshooting, as it:

Displays immediate feedback on the success or failure of each deployment step.
Highlights specific error messages and codes, helping you quickly identify and understand issues.
Offers links to detailed documentation and guides for resolving common problems.
Keeps a log of past notifications, allowing you to track and review previous errors and their resolutions.

By actively monitoring the Notification Center, you can promptly address issues as they arise, ensuring a smoother deployment process. Learn more about Managing Events with the Notification Center.

Current behavior 🔗

Deploy needs Deploy Design, a non-empty design, and a Meshery you run. kanvas.new shows a prompt titled SELF-HOSTED FEATURE. If you select no Kubernetes context, Kanvas deploys to all connected clusters. The dialog title is Deploy design "<name>". Deploying does not need Meshery Operator. The same design applied again updates objects in place.

Every created resource is labeled design.meshery.io/id and annotated design.meshery.io/version and component.meshery.io/id. meshery-server-1096 means no selected context resolved to a connected cluster. meshery-server-1073 means the connection is not in the environment or cannot reach the cluster. meshery-server-1095 means the kubeconfig is invalid. No environments found means the organization has no environment (Create Environment and Edit Environment). If the Finish step spins and never reports, the request failed before an event, often an expired session.