Update documentation for Kubernetes cluster creation, load balancer V…

[godsonten]

…M attachment, and object storage naming

What changed

Why

---

Summary by CodeRabbit

• Documentation
  • Updated Kubernetes cluster creation steps to include Kubernetes version and storage type selection.
  • Clarified how to select multiple VMs during load balancer creation and add backend instances later.
  • Renamed the Object Storage section to “Object Storage (Object Store)” for clarity.

[coderabbitai]

📝 Walkthrough

Walkthrough

The documentation updates revise Kubernetes cluster creation steps, clarify load balancer VM selection and backend additions, and rename an object storage section heading.

Changes

Public cloud documentation

Layer / File(s)	Summary
Kubernetes creation flow src/content/docs/public-cloud/kubernetes/create-cluster.md	Adds version and storage type selections, then renumbers the remaining cluster creation steps.
Load balancer VM guidance src/content/docs/public-cloud/load-balancer/index.md	Explains selecting multiple same-network VMs during creation and adding backend instances through Add New Policies.
Object storage terminology src/content/docs/public-cloud/storage/object-storage/create-bucket.md	Renames the section heading to “Object Storage (Object Store)”.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

• zsoftly/zcp-docs#6: Updates the same object storage documentation page.
• zsoftly/zcp-docs#28: Adds screenshots for the Kubernetes cluster creation flow.
• zsoftly/zcp-docs#46: Also restructures the Kubernetes creation steps.

Suggested reviewers: ditahm6, clintonche, ditahkk

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description leaves the required What changed and Why sections empty, so it does not satisfy the template.	Add a concise What changed summary and a Why section explaining the motivation or linked issue, while keeping the required template headings.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title is specific and matches the PR’s documentation updates for Kubernetes, load balancer, and storage.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch issues/386-docs-bug-fix

---

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.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@src/content/docs/public-cloud/load-balancer/index.md`:
- Line 38: In the Load Balancer documentation sentence near “Add New Policies,”
replace the British spelling “afterwards” with the American-English spelling
“afterward.”

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: bf9ca552-a974-4383-8d9b-faa208f8e87f

📥 Commits

Reviewing files that changed from the base of the PR and between 5b34b5c and 785a0cc.

📒 Files selected for processing (3)

• src/content/docs/public-cloud/kubernetes/create-cluster.md
• src/content/docs/public-cloud/load-balancer/index.md
• src/content/docs/public-cloud/storage/object-storage/create-bucket.md

[coderabbitai]

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Use the American-English spelling “afterward”.

-To add more backend instances afterwards, open the Load Balancer and click **Add New Policies**.
+To add more backend instances afterward, open the Load Balancer and click **Add New Policies**.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	backend instances afterwards, open the Load Balancer and click **Add New Policies**.
	To add more backend instances afterward, open the Load Balancer and click **Add New Policies**.

🧰 Tools

🪛 LanguageTool

[locale-violation] ~38-~38: In American English, ‘afterward’ is the preferred variant. ‘Afterwards’ is more commonly used in British English and other dialects.
Context: ...balancer. To add more backend instances afterwards, open the Load Balancer and click **Add...

(AFTERWARDS_US)

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/content/docs/public-cloud/load-balancer/index.md` at line 38, In the Load
Balancer documentation sentence near “Add New Policies,” replace the British
spelling “afterwards” with the American-English spelling “afterward.”

Source: Linters/SAST tools