Update README.md

[allanice001]

User description

Add a safety step to delete an existing cluster named captain

---

PR Type

Enhancement

---

Description

• Add cluster deletion step before creation to prevent conflicts
• Ensure clean cluster setup by removing existing 'captain' cluster

---

Changes walkthrough 📝

	Relevant files
Enhancement	README.md Add cluster deletion safety step                                                  README.md • Added k3d cluster delete captain command before cluster creation • Modified the installation command chain to include cleanup step +1/-1

---

Need help?

Type /help how to ... in the comments thread for any questions about Qodo Merge usage.

Check out the documentation for more information.

[pull-request-checklist-buddy]

PR Checklist (required):

• Is the README.md up to date?
• Code tested appropriately (end-to-end considered)?
• Did you review any AI provided feedback?

[codiumai-pr-agent-free]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Command Safety The added deletion command will fail silently if the cluster doesn't exist. Consider adding error handling or a check if the cluster exists before attempting deletion. curl https://raw.githubusercontent.com/GlueOps/k3d/main/k3d-config.yaml -o k3d-config.yaml && k3d cluster delete captain && k3d cluster create --config k3d-config.yaml && bash <(curl -sL https://raw.githubusercontent.com/GlueOps/k3d/main/add-machineid.sh) </details> </td></tr> </table>

[codiumai-pr-agent-free]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
General	Handle non-existent cluster gracefully The k3d cluster delete captain command will fail for first-time users who don't have a cluster named "captain" yet. Consider making this step conditional to prevent errors for new users. README.md [14] -curl https://raw.githubusercontent.com/GlueOps/k3d/main/k3d-config.yaml -o k3d-config.yaml && k3d cluster delete captain && k3d cluster create --config k3d-config.yaml && bash <(curl -sL https://raw.githubusercontent.com/GlueOps/k3d/main/add-machineid.sh) +curl https://raw.githubusercontent.com/GlueOps/k3d/main/k3d-config.yaml -o k3d-config.yaml && k3d cluster delete captain 2>/dev/null || true && k3d cluster create --config k3d-config.yaml && bash <(curl -sL https://raw.githubusercontent.com/GlueOps/k3d/main/add-machineid.sh) Apply / Chat Suggestion importance[1-10]: 9 __ Why: The suggestion correctly identifies that the k3d cluster delete captain command will fail if the cluster doesn't exist, which would halt the entire command chain due to &&. The proposed fix using || true is a robust way to ensure the script continues, significantly improving the user experience for first-time setups.	High
More

[venkatamutyala]

@allanice001 just need to fix the commit messages: https://www.conventionalcommits.org/en/v1.0.0/

Current checks:
https://github.com/GlueOps/github-workflows/blob/main/.github/workflows/glueops-basic-pr-checks.yml

• Feel free to PR things we should consider adding

[hamzabouissi]

@allanice001 what's the status of this pr
@venkatamutyala FYI