Apply YAML

Apply YAML (a Kubius Pro feature) lets you create or update Kubernetes objects from a manifest - paste it or load a file, validate it against the cluster, then apply. Open it from the FEATURES band in the sidebar.

It uses server-side apply (the same mechanism as kubectl apply --server-side, fieldManager: kubius): objects are created or updated by name, validated by the API server’s own schema and admission controllers.

Using it

1. Paste your YAML into the editor, or click Choose file… to load a .yaml/.yml.
2. Click Validate (dry-run) - the safe default. Kubius sends a server-side dry-run for each document: the API server fully validates it (schema + admission) but nothing is persisted.
3. Read the per-document results - a green ✓ “would be applied”, or a red ✗ with the API server’s own error message (which you can select and copy).
4. If every document passes, an Apply to cluster button appears. Click it to apply for real.
5. After a successful apply, each result has a View button that jumps to that resource’s list - create a Deployment, click View, and you land in the Deployments section.

Multiple documents

Separate objects with --- on its own line; Kubius applies each independently and reports a result per object. Built-in types and CRDs both work - the resource path (and whether it’s namespaced) is resolved from the cluster’s API discovery.

Namespaces

Each namespaced object uses the metadata.namespace in its YAML. If that’s omitted, Kubius falls back to the namespace you’re currently scoped to in the app (or default). Cluster-scoped kinds ignore namespace.

Requirements & notes

• Each document needs apiVersion, kind and metadata.name (server-side apply targets objects by name).
• Apply respects RBAC - you can only apply what your credentials permit; a forbidden apply reports the API’s 403 message.
• Dry-run never changes anything, so it’s safe to validate as often as you like before committing.