Add usage doc for VolumeSnapshot

[Rohit-0505]

• Update usage-guides/storage.md forVolumeSnapshot resource

Summary by CodeRabbit

• Documentation
  • Clarified Kubernetes cloud controller manager docs (reflowed EnsureLoadBalancer section for readability).
  • Fixed capitalization in networking guide ("IronCore").
  • Added VolumeSnapshot resource docs with example and key fields; expanded storage overview to include Buckets and VolumeSnapshots and refined related descriptions.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[afritzler]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[coderabbitai]

Walkthrough

Documentation updates across three files: rewording of EnsureLoadBalancer bullets in cloud-controller-manager, capitalization fix for IronCore in networking guide, and addition of a VolumeSnapshot resource section (with example and key fields) plus related wording adjustments in storage docs.

Changes

Cohort / File(s)	Summary
Kubernetes CCM docs docs/iaas/kubernetes/cloud-controller-manager.md	Reflowed and clarified bullet ordering under EnsureLoadBalancer: existence check/creation, creation of LoadBalancerRouting after LoadBalancer, and LoadBalancer type handling (Public vs Internal) with internal annotation note. No semantic changes.
Networking guide docs/iaas/usage-guides/networking.md	Capitalization correction: "Ironcore" → "IronCore" in post-reconciliation Network resource description.
Storage guide additions docs/iaas/usage-guides/storage.md	Added VolumeSnapshot resource section with example and key field volumeRef; expanded resource list to include Buckets and VolumeSnapshots; minor wording/capitalization tweaks across VolumePool, BucketPool, and BucketClass descriptions.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~15 minutes

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The description is minimal and lacks the expected template structure with proposed changes sections and issue references as specified in the repository template.	Expand the description to follow the template structure with bullet points under 'Proposed Changes' and include issue reference (Fixes #).

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically summarizes the main change: adding VolumeSnapshot usage documentation to the storage guide.
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.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@docs/iaas/usage-guides/storage.md`:
- Around line 2-9: Change the inconsistent capitalization of the product name:
find the occurrence of "Ironcore" in the storage guide paragraph (the sentence
mentioning "VolumeSnapshots" and "Volume") and replace it with the correct
branded "IronCore" so it matches other docs and the existing uses of "IronCore",
e.g., in the context around VolumeSnapshots and Volume provisioning.

🧹 Nitpick comments (1)

docs/iaas/usage-guides/storage.md (1)

180-200: Consider expanding the VolumeSnapshot documentation.

The new VolumeSnapshot section is a good addition, but it's noticeably more minimal than other resource documentation in this file (compare with Volume, Bucket, NetworkInterface in networking.md). Consider adding:

1. Status information: What happens after a VolumeSnapshot is created? Does it have a status field showing state (e.g., Ready, Pending, Failed)?
2. Additional spec fields: Are there other fields like volumePoolRef or size constraints that users should know about?
3. Usage section: How do users restore from a snapshot or provision a new Volume from it (as mentioned in line 7)?
4. Example with status: Similar to other resources, showing both spec and status after reconciliation would be helpful.

This would bring the VolumeSnapshot documentation to the same level of completeness as other resources in this guide.