LimitRange YAML Generator

A LimitRange sets sane defaults and guardrails for the resources pods and containers can use in a namespace. The LimitRange YAML Generator writes that manifest from a form so you do not have to recall the core/v1 schema.

You set the LimitRange name and namespace, choose a limit type (Container, Pod or PersistentVolumeClaim), and then set the CPU and memory ceilings and floors you want: max, min, default and defaultRequest. Only the fields you fill are emitted. The resulting YAML is valid core/v1.

The name is validated as an RFC 1123 label and the namespace, if set, must be valid too. At least one resource constraint is required. Problems are reported in a clear panel. Everything runs locally and nothing is uploaded.

• Limit types - Container, Pod, PersistentVolumeClaim.
• Per resource - cpu and memory with max, min, default, defaultRequest.
• Flexible values - 500m, 1, 1Gi, 512Mi.
• core/v1 - correct schema.
• Validation - RFC 1123 name, namespace and at least one constraint.
• Copy / Download / Print - get limitrange.yaml wherever you need it.

1. Name the LimitRange. Type a valid RFC 1123 name.
2. Set the namespace and type.
3. Fill the CPU/memory constraints. Only the fields you need.
4. Watch the preview and export.

Example 1 - container defaults. type Container, default cpu 500m, default memory 512Mi.

Example 2 - bounds. max cpu 1, min memory 64Mi.

Example 3 - pod type. type Pod, max cpu 2.

Example 4 - default request. defaultRequest cpu 100m.

Example 5 - memory heavy. max memory 4Gi, min 128Mi.

• Correct schema - valid core/v1 LimitRange.
• Default and bounds - max/min/default/defaultRequest.
• Validated - names and at least one constraint checked.
• Clean output - empty fields omitted.
• Private - everything runs in the browser.
• Copy, download or print - get the manifest where you need it.