Idea: Resource creation

[nadaverell]

Problem

Radar currently supports editing existing resources (YAML editor with apply) and deleting them — but there is no way to create a new resource from scratch. If you want to create a ConfigMap, a new Deployment, a NetworkPolicy, or any other resource, you have to leave Radar and use kubectl apply or another tool.

For a tool that aims to be a full Kubernetes UI — not just a read-only viewer — this is a meaningful gap.

Idea

Basic resource creation

A "Create" action (accessible from resource list views and the command palette) that opens the YAML editor pre-populated with a skeleton for the selected resource kind. The user fills it in and applies it.

This is a thin addition on top of the existing YAML editor infrastructure — the backend already has a dynamic client that can handle arbitrary resource kinds.

Resource templates

As a follow-on: the ability to save any resource as a reusable template with {{variable}} placeholders. When creating from a template, Radar prompts for variable values before applying.

Useful for teams that repeatedly create similar resources (jobs, configmaps, namespaces with standard labels, etc.) with slight variations.

Why it matters

Right now Radar covers observe → debug → operate (restart, scale, rollback, port-forward, exec). Resource creation is the missing piece of the operate story. Without it, users always need a second tool open for any provisioning work — which breaks the "one place for everything" experience.

[nadaverell]

Shipped — the CreateResourceDialog component is live. You can create any resource type via the Create action in resource list views and the command palette, with the YAML editor pre-populated with a skeleton.

Templates with variable placeholders (the follow-on idea in this discussion) are not shipped yet. If that's still interesting, happy to track it as a separate discussion.

Closing for now.