Show LimitRange defaults and constraints in resource and Namespace drawers #1660

Problem

LimitRanges define namespace resource defaults and constraints. Radar already reads them and uses them in audits, but has no dedicated detail renderer; users must inspect the object to understand the rules.

Goal

Add a read-only LimitRange drawer showing entries by type (Container, Pod or PersistentVolumeClaim), with each resource's minimum, maximum, default request, default limit and maximum limit/request ratio where present. Add a Namespace drawer section summarizing its LimitRanges and linking to them, so users can discover the rules from the namespace they are troubleshooting.

In the existing resource requests/limits section of Pod and Deployment details, add a small contextual link labeled “Namespace defaults & constraints” to the relevant namespace rules. Do not duplicate the policy tables or add a prominent banner.

Scope and considerations

• Reuse existing drawer sections and resource-quantity formatting. Keep unset fields distinct from zero; retain units and resource names. Ratios are dimensionless, not resource quantities.
• Show each declared entry without inventing a merged effective policy. These are current rules, not proof of which defaults were applied to an existing Pod. A LimitRange has no health status to invent.
• For Deployments, describe rules for admission of their Pods, not the Deployment object itself. The link shows current namespace rules, not historical attribution; other admission mechanisms may also have modified a Pod's resources.
• No new page, editor, audit detector or topology. Reuse the existing Namespace quota-section data-fetching pattern; distinguish loading/failed reads from an empty list and respect resource access.

Start with packages/k8s-ui/src/components/resources/renderers/ and components/shared/ResourceRendererDispatch.tsx under packages/k8s-ui/src/. For Namespace wiring, see web/src/api/quotas.ts and the host NamespaceRenderer. Follow the resource-view parts of the integration guide.

Test multiple entry types, partial fields, zero values, quantities/ratios and Namespace loading/empty/error/access states. Include local-cluster screenshots of the LimitRange/Namespace drawers and the contextual Pod/Deployment link; verify navigation and missing/forbidden rule access; no third-party controller is needed.

Kubernetes LimitRange documentation