Updated disabling instructions

[pavangudiwada]

Summary by CodeRabbit

• Documentation
  • Improved and clarified instructions for disabling the Robusta Alerts UI, including step-by-step guidance and explicit commands for listing and deleting related resources.

[coderabbitai]

Walkthrough

The documentation for disabling the Robusta Alerts UI was revised to provide more detailed and step-by-step instructions. The update separates the process into clear steps, adds specific commands for identifying and deleting related resources, and improves the overall clarity and completeness of the guidance.

Changes

File(s)	Change Summary
docs/setup-robusta/alertsui.rst	Expanded and restructured instructions for disabling Robusta Alerts UI, adding explicit cleanup steps

Sequence Diagram(s)

No sequence diagram generated as the changes are limited to documentation updates and do not affect control flow or introduce new features.

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (3)

docs/setup-robusta/alertsui.rst (3)

73-76: Refine the disabling section header and intro sentence.
The current fragment “If you choose to stop using the Robusta Alerts UI” reads as a sentence fragment. For consistency, consider rephrasing to an imperative form—e.g.:

To disable the Robusta Alerts UI:

and follow with the numbered steps, ensuring proper indentation under the list.

---

80-81: Explicitly reference the full CRD resource type.
Using prometheusrules alone can be ambiguous. Recommend specifying the group for clarity:

kubectl get prometheusrules.monitoring.coreos.com -A | grep robusta-prometheus

Optionally, you can output only the names/namespaces for scripting:

kubectl get prometheusrules.monitoring.coreos.com -A -o custom-columns=NAME:.metadata.name,NAMESPACE:.metadata.namespace

---

85-87: Clarify placeholders and offer batch deletion snippet.
The placeholder robusta-prometheus.rules<VALUE> and <NAMESPACE> may be unclear. Rename <VALUE> to <RULE_NAME_SUFFIX> and add an example. To delete all matching rules in one go, you could also use:

kubectl get prometheusrules.monitoring.coreos.com -A --no-headers \
 | awk '/robusta-prometheus.rules/{print $1, $2}' \
 | xargs -n2 sh -c 'kubectl delete prometheusrules.monitoring.coreos.com "$0" -n "$1"'

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between fd44578 and 14f35ed.

📒 Files selected for processing (1)

• docs/setup-robusta/alertsui.rst (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (4)

• GitHub Check: run_tests
• GitHub Check: run_tests
• GitHub Check: Deploy docs
• GitHub Check: Deploy docs