Skip to content

Diagnose blueprint sync

Arguments: $ARGUMENTS

A blueprint is an addon stack (dependencies form a graph) that Rafay syncs to Kubernetes. Required inputs are the cluster name and the project name (always supply the project explicitly). After rafay_get on the cluster, read the blueprint name and version from the cluster object—then load that blueprint and compare to cluster_addon list sync state; that list usually shows which addons failed or are stuck. Use kubectl only when you need on-cluster evidence.

Inputs

Key Required Description
cluster_name Yes Rafay cluster resource name.
project_name Yes Rafay project that owns the cluster. Always supply explicitly—do not rely on RAFAY_PROJECT or other defaults.

If cluster_name or project_name is missing, stop and ask the user to supply both:

cluster_name: <cluster>
project_name: <project>

MCP mapping: cluster_name → name on rafay_get / rafay_list / rafay_execute when resource_type=cluster; project_name → project-name on every Rafay call (required).

Prerequisites

  • rafay MCP authenticated; pass project-name on every call using the supplied project_name (do not skip it because RAFAY_PROJECT is set).
  • Before calling tools, read schemas from the host’s rafay MCP tool descriptors.

Steps

  1. Inputs — Confirm cluster_name and project_name from the user (or the YAML block above). Do not require the user to supply a blueprint name; it should come from the cluster.

  2. Cluster — rafay_get with resource_type=cluster, name = cluster_name, and project-name = project_name. From the payload, take the blueprint name and version (or equivalent fields the API uses—use the returned field names verbatim). If no blueprint is attached or fields are missing, say so and stop or ask for corrected cluster/project context; only then consider rafay_list resource_type=blueprint as a fallback for discovery, not as the default path.

  3. Blueprint — rafay_get with resource_type=blueprint, name = blueprint name from step 2, and project-name = project_name.

  4. Versions — rafay_list with resource_type=blueprint_version, name = that same blueprint name, and project-name = project_name. Relate the cluster’s version to this list.

  5. Addons on cluster — rafay_list with resource_type=cluster_addon, name = cluster_name, and project-name = project_name. This list is the primary place to see what failed or is stuck: use status, conditions, messages, or other fields exactly as the API returns them. Compare to the blueprint version from steps 2–4; note pending or mismatched addons and dependency order if the response shows it.

  6. kubectl (optional) — If cluster_addon data is not enough: rafay_execute with resource_type=cluster, action=kubectl, cluster name = cluster_name, and project-name = project_name.

  7. Summarize — What the cluster reports for blueprint binding, what the blueprint/version catalog shows, vs cluster_addon sync; drift, blockers, and next steps. On auth errors, 404s, or missing blueprint on the cluster, state the blocker and what is missing.