[devantler]

🤖 Generated by the Daily AI Assistant

Why

The KRO Tenant abstraction (see the ADR) does not yet emit a namespace ResourceQuota or per-container LimitRange — a standard multi-tenancy guardrail against a tenant consuming unbounded cluster resources.

What

Adds optional resourceQuota / limitRange inputs to the Tenant RGD schema, each with its own enabled toggle (default false). When enabled, the RGD emits the matching object in the tenant namespace; existing tenants are unaffected. Follows the RGD's own already-proven boolean-toggle pattern (externalDns/sops), so it needed no new kro features — statically validated via ksail workload validate (the RGD file validates cleanly; the 3 unrelated failures in the same run are a network-fetch timeout on an unrelated schema and a pre-existing HelmRelease YAML issue, both present on unmodified main).

Fixes #2522
Part of #1932

Documented in docs/tenant-abstraction.md and pointed to from docs/TENANTS.md per the issue's acceptance criteria.

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR extends the KRO Tenant ResourceGraphDefinition schema with two new optional guardrail types, TenantResourceQuota and TenantLimitRange, each with an enabled toggle (defaulting to false) and default resource values. These are wired into spec.resourceQuota and spec.limitRange on the Tenant schema, and conditionally render a ResourceQuota and LimitRange in the tenant namespace when enabled. Documentation in tenant-abstraction.md marks this follow-up as completed and expands details on the ExternalSecret follow-up. TENANTS.md gains a note describing a KRO-based fast path for tenant onboarding alongside the existing pre-KRO flow.

Possibly related PRs

• devantler-tech/platform#2519: Updates the same "Consequences → Follow-ups" section in docs/tenant-abstraction.md, including the ResourceQuota/LimitRange and ExternalSecret follow-up items.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	The changes satisfy #2522 by adding optional inputs, conditional ResourceQuota/LimitRange rendering, and docs updates.
Out of Scope Changes check	✅ Passed	The changes stay focused on the Tenant guardrails and related documentation, with no clear unrelated additions.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check	✅ Passed	The title accurately summarizes the main change: optional ResourceQuota/LimitRange guardrails for the KRO Tenant RGD.
Description check	✅ Passed	The description clearly matches the changes and objectives, including the optional guardrails, docs updates, and linked issue context.

---

_{Comment @coderabbitai help to get the list of available commands.}

[botantler-1]

🎉 This PR is included in version 1.109.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀