docs(talm): update talm init syntax for mandatory --preset and --name flags

[lexfrei]

Summary

Update documentation to reflect breaking changes in talm from PR #75 and PR #86:

• Add mandatory --preset flag (previously defaulted to "generic")
• Add mandatory --name flag (previously derived from directory name)
• Use different directory and cluster names to clarify they are separate concepts

Changed files

• content/en/docs/install/kubernetes/talm.md
• content/en/blog/2025-04-28-a-simple-way-to-install-talos-linux-on-any-machine-with-any-provider.md
• content/en/docs/install/providers/hetzner.md
• content/en/docs/install/providers/oracle-cloud.md
• content/en/docs/install/providers/servers-com/_index.md

References

• Makes the preset flag mandatory talm#75
• feat(init)!: require --name flag for cluster name talm#86

Summary by CodeRabbit

• Documentation
  • Updated Talos Linux installation documentation across multiple providers with standardized directory naming conventions for consistency.
  • Revised configuration initialization commands with explicit flags for preset and cluster name parameters.
  • Enhanced setup procedures in blog posts and provider-specific installation guides.

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

[coderabbitai]

Walkthrough

Updates documentation across multiple installation guides to standardize Talm initialization configuration. Changes include renaming working directories to more descriptive names and updating Talm commands to use explicit long-form flags (--preset and --name) instead of short forms, while maintaining consistent command patterns.

Changes

Cohort / File(s)	Summary
Provider documentation content/en/docs/install/providers/hetzner.md, oracle-cloud.md, servers-com/_index.md	Updated Talm initialization: directory renamed to descriptive names (hetzner-cluster, cozystack-cluster); init command changed from short flag -p to explicit --preset and --name flags with appropriate cluster identifiers
Installation guides content/en/docs/install/kubernetes/talm.md	Directory creation standardized from cluster1 to cozystack-cluster; Talm init command updated to include explicit --name mycluster flag
Blog documentation content/en/blog/2025-04-28-a-simple-way-to-install-talos-linux-on-any-machine-with-any-provider.md	Working directory changed to talos-config; Talm init command updated to talm init --preset generic --name talos

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically describes the main change: updating documentation to reflect the talm init syntax changes with mandatory --preset and --name flags.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 655a414 and eca7dd0.

📒 Files selected for processing (5)

• content/en/blog/2025-04-28-a-simple-way-to-install-talos-linux-on-any-machine-with-any-provider.md
• content/en/docs/install/kubernetes/talm.md
• content/en/docs/install/providers/hetzner.md
• content/en/docs/install/providers/oracle-cloud.md
• content/en/docs/install/providers/servers-com/_index.md

🔇 Additional comments (5)

content/en/docs/install/kubernetes/talm.md (1)

84-86: ✓ Initialization syntax is correctly updated.

The command syntax properly reflects mandatory --preset and --name flags, and the directory naming convention is now more descriptive.

content/en/docs/install/providers/servers-com/_index.md (1)

155-162: ✓ Consistent with main Talm guide.

Directory naming and initialization syntax are properly aligned with the updated Talm requirements and match the pattern established in the main documentation.

content/en/docs/install/providers/oracle-cloud.md (1)

260-267: ✓ Consistent with provider documentation pattern.

The directory structure and initialization command correctly reflect the mandatory --preset and --name flags, consistent across provider guides.

content/en/docs/install/providers/hetzner.md (1)

263-270: ✓ Provider-specific naming is appropriate.

The use of hetzner-cluster directory and --name hetzner appropriately reflects the provider-specific context while maintaining consistency with the command syntax pattern across all provider guides.

content/en/blog/2025-04-28-a-simple-way-to-install-talos-linux-on-any-machine-with-any-provider.md (1)

134-136: ✓ Generic initialization syntax is appropriate for broad audience.

The use of --preset generic and --name talos is fitting for a blog post intended to be broadly applicable across different infrastructure scenarios. The initialization command correctly reflects the mandatory flag requirements.

---

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

[gemini-code-assist]

Summary of Changes

Hello @lexfrei, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates various documentation pages to align with recent breaking changes in the talm tool's initialization process. It ensures that all examples and instructions correctly reflect the new mandatory --preset and --name flags for the talm init command, improving clarity and accuracy for users. Additionally, the examples have been refined to clearly differentiate between directory names and cluster names.

Highlights

• Mandatory Flags for talm init: The talm init command now requires both the --preset and --name flags, which were previously optional or automatically derived.
• Documentation Alignment: All relevant documentation files have been updated to reflect the new mandatory flags and the correct syntax for talm init.
• Improved Clarity in Examples: Examples now use distinct directory and cluster names to clearly illustrate that these are separate concepts, enhancing user understanding.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates the documentation for the talm init command to reflect the new mandatory --preset and --name flags. The changes are applied consistently across all relevant markdown files, and the distinction between directory names and cluster names is now clearer. I've added a couple of suggestions to use more provider-specific names in the examples, which should further improve clarity for readers. Overall, this is a solid and necessary update to the documentation.

[netlify]

✅ Deploy Preview for cozystack ready!

Name	Link
🔨 Latest commit	eca7dd0
🔍 Latest deploy log	https://app.netlify.com/projects/cozystack/deploys/694a5329d8b7c4000971fcbb
😎 Deploy Preview	https://deploy-preview-386--cozystack.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

Actionable comments posted: 0

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

content/en/docs/install/kubernetes/talm.md (1)

89-96: Update outdated statement about cluster naming.

Line 92 states "the name of the chart is used as the name for the newly created cluster," but with the mandatory --name flag, the cluster name is now explicitly set during initialization, not derived from the chart metadata.

🔎 Proposed fix

- `Chart.yaml` - a file containing the common information about your project; the name of the chart is used as the name for the newly created cluster.
+ `Chart.yaml` - a file containing the common information about your project; the cluster name is determined by the `--name` flag passed to `talm init`.

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 655a414 and eca7dd0.

📒 Files selected for processing (5)

• content/en/blog/2025-04-28-a-simple-way-to-install-talos-linux-on-any-machine-with-any-provider.md
• content/en/docs/install/kubernetes/talm.md
• content/en/docs/install/providers/hetzner.md
• content/en/docs/install/providers/oracle-cloud.md
• content/en/docs/install/providers/servers-com/_index.md

🔇 Additional comments (5)

content/en/docs/install/kubernetes/talm.md (1)

84-86: ✓ Initialization syntax is correctly updated.

The command syntax properly reflects mandatory --preset and --name flags, and the directory naming convention is now more descriptive.

content/en/docs/install/providers/servers-com/_index.md (1)

155-162: ✓ Consistent with main Talm guide.

Directory naming and initialization syntax are properly aligned with the updated Talm requirements and match the pattern established in the main documentation.

content/en/docs/install/providers/oracle-cloud.md (1)

260-267: ✓ Consistent with provider documentation pattern.

The directory structure and initialization command correctly reflect the mandatory --preset and --name flags, consistent across provider guides.

content/en/docs/install/providers/hetzner.md (1)

263-270: ✓ Provider-specific naming is appropriate.

The use of hetzner-cluster directory and --name hetzner appropriately reflects the provider-specific context while maintaining consistency with the command syntax pattern across all provider guides.

content/en/blog/2025-04-28-a-simple-way-to-install-talos-linux-on-any-machine-with-any-provider.md (1)

134-136: ✓ Generic initialization syntax is appropriate for broad audience.

The use of --preset generic and --name talos is fitting for a blog post intended to be broadly applicable across different infrastructure scenarios. The initialization command correctly reflects the mandatory flag requirements.