Add Grove PodCliqueSet (grove.io/v1alpha1) Karta example

[shmuel-runai]

Closes #65

Reference Karta definition for the Grove PodCliqueSet CRD covering
status mappings, clique/scaling-group child components, additional
child kinds, and gang-scheduling optimization instructions.

Summary by CodeRabbit

Release Notes

• Documentation
  • Added an example configuration file demonstrating how to set up and manage Grove PodCliqueSet workloads with replica scaling, status tracking, and pod co-scheduling capabilities.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Enterprise

Run ID: 9352474a-b88a-4b47-b963-92f44a0202a6

📥 Commits

Reviewing files that changed from the base of the PR and between c8d543d and 8cd68de.

📒 Files selected for processing (1)

• docs/examples/grove-podcliqueset.yaml

---

Walkthrough

A new documentation example YAML file defines a complete Karta workload specification for Grove PodCliqueSet, including replica-based status conditions, child component definitions with scaling formulas, additional resource kinds, and gang-scheduling pod group membership rules keyed by labels.

Changes

Grove PodCliqueSet Karta Example

Layer / File(s)

Summary

Grove PodCliqueSet Karta workload example specification docs/examples/grove-podcliqueset.yaml

Complete Karta workload example for PodCliqueSet specifies status condition mappings based on spec.replicas and status.availableReplicas, defines two primary child component types (standalone PodClique and PodCliqueScalingGroup) with scaling replica formulas and selector paths, registers additional child kinds for ownership traversal, and configures gang-scheduling pod group membership using label-based grouping keys (grove.io/podcliqueset-name and replica index labels).

Estimated Code Review Effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Poem

A Karta tale of Grove's design, 🐰
PodCliqueSet dancing in perfect time,
Cliques grouped and scaled with care,
Pod gang-scheduling beyond compare! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The pull request title accurately summarizes the main change: adding a Grove PodCliqueSet Karta example, which directly matches the changeset content.
Linked Issues check	✅ Passed	The pull request implements all coding requirements from issue #65: status mappings, clique/scaling-group child components, additional child kinds, and gang-scheduling instructions are all present in the new YAML specification.
Out of Scope Changes check	✅ Passed	All changes are directly related to issue #65 objectives. The single file added (docs/examples/grove-podcliqueset.yaml) contains only the Grove PodCliqueSet Karta example as requested.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch RUN-38840/main-grove-pcs-example

---

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

[ronlv10]

Overall looks good , left a few comments

[ronlv10]

could it be that .spec.replicas is missing or 0 ? what should the phase in this case ?

[ronlv10]

seems like you could use

          podSpecPath: .spec.template.cliques[].spec.podSpec

 but the issue is the path to metadata that missing ?  wondering maybe we could add Fragmented metadata  - would it help you to set the path to pod spec and just paths to annotations and labelsr ? currenly we enforce either podSpecPath , podTemplateSpecPath  or fragmentedPodSpecDefinition but we could add fragmentedMetadataDefinition (hope I want clear)