Deploy from YAML

What the UI does

The Advanced - YAML Manifest screen uses Monaco Editor with YAML parsing and CRD schema-based IntelliSense. On submit, the UI calls POST /api/clusters/yaml with the raw YAML string. The Admin Server parses the manifest, requires metadata.name and metadata.namespace, checks that the cluster does not already exist, and then applies the YAML through the Kubernetes repository.

Create from YAML

Open Deployments > Create Deployment.
Choose Advanced - YAML Manifest.
Edit the manifest.
Confirm the UI shows Valid YAML.
Select Deploy Cluster.

Required metadata

The backend rejects manifests that do not include both fields:

metadata:
  name: falkordb
  namespace: demo

The backend also rejects YAML creation when a cluster with the same name already exists in the namespace.

Default template

The editor starts with a KubeBlocks Cluster manifest using:

apiVersion: apps.kubeblocks.io/v1
kind: Cluster
spec.clusterDef: falkordb
spec.topology: replication
Component falkordb with 2 replicas
Component falkordb-sent with 3 replicas
terminationPolicy: Delete

Validate

kubectl get clusters.apps.kubeblocks.io -n <namespace>
kubectl get pods -n <namespace>

If creation fails, check the Admin UI toast and Admin Server logs. YAML parse errors are shown in the editor before submit; Kubernetes validation errors are returned by the backend after submit.

⌘I

Get started

Install

Authentication

Deploy databases

Operations

Upgrade and uninstall

Troubleshooting

What the UI does

Create from YAML

Required metadata

Default template

Validate

​What the UI does

​Create from YAML

​Required metadata

​Default template

​Validate

What the UI does

Create from YAML

Required metadata

Default template

Validate