Troubleshooting Kanvas

Learn to Troubleshoot the Kanvas

Upon Meshery extension’s first load, a GET request initializes the Kanvas plugin. Errors are classified into two types: plugin not found or built on a different version. Kanvas loads, and Designer is functional if no errors occur.

GraphQL queries fetch header data and view data for the Operator canvas. Checks ensure data types and properties are correct, enabling canvas display. If no clusters are connected, a modal prompts the user to select one.

  • MODE STATE: Operator and Designer: Inactive, Not Interactable.
  • CAUSED WHEN: plugin.so is not in the desired folder.
  • REMEDIATION: Confirm plugin versions, run make dev or make prod on the local meshery-extension folder.
  • MODE STATE: Operator and Designer: Inactive, Not Interactable.
  • CAUSED WHEN: go.mod mismatches between meshery/meshery and layer5labs/meshery-extensions.
  • REMEDIATION: Ensure identical go.mod files and plugin version matching.
  • MODE STATE: Operator: Active, Not Interactable; Designer: Active, Interactable.
  • CAUSED WHEN: No active Kubernetes cluster connections.
  • REMEDIATION: Connect a Kubernetes cluster from settings.
  • MODE STATE: Operator: Active, Not Interactable; Designer: Active, Interactable.
  • CAUSED WHEN: Meshery Broker lacks an external IP address or networking issues.
  • REMEDIATION: Delete meshery-meshsync pod, use Docker Desktop/Kind/Minikube/external cloud provider.
  • MODE STATE: Operator: Inactive, Not Interactable; Designer: Active, Interactable.
  • CAUSED WHEN: Unable to save/query database.
  • REMEDIATION: Use System Reset button or remove the config folder and rebuild Meshery.
  • MODE STATE: Operator and Designer: Active, Interactable.
  • CAUSED WHEN: Meshery and Kanvas version mismatches.
  • REMEDIATION: Pull/build the latest Kanvas, update Mesheryctl and Meshery.

Recent Discussions on Kanvas