[ROB-1923] improve irsa docs

[Avi-Robusta]

No description provided.

[coderabbitai]

Walkthrough

Updates the AWS AMP configuration documentation to consolidate IRSA setup into a single “Configure Robusta” step, revise YAML examples with a new toolsets.prometheus/metrics.config block, adjust globalConfig keys (including cluster-wide labels), and renumber Quick Start steps while retaining the Access Keys alternative.

Changes

Cohort / File(s)	Summary
Docs: AWS AMP configuration docs/configuration/metric-providers-aws.rst	Rewrote Quick Start to a unified IRSA-based “Configure Robusta”; added toolsets.prometheus/metrics.config block with AMP URL, region, service name, SSL, additional labels, and enable flag; updated globalConfig Prometheus URL and prometheus_additional_labels; changed step numbering; kept Access Keys alternative.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~7 minutes

Possibly related PRs

• [ROB-1923] amp irsa support #1907 — Also updates AWS AMP docs for IRSA-based auth and related Prometheus/AWS configuration in the same area.

Suggested reviewers

• arikalon1
• moshemorad

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch update_irsa_docs

---

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.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

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

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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: 2

🧹 Nitpick comments (1)

docs/configuration/metric-providers-aws.rst (1)

88-89: De-duplicate cluster label configuration and standardize quoting

Keep labels in one place (recommended: globalConfig.prometheus_additional_labels) and use consistent quoting.

-           prometheus_additional_labels: # Add cluster label to all queries
-               cluster: 'my_cluster_name'
+           prometheus_additional_labels: # Add cluster label to all queries
+               cluster: "my_cluster_name"

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 748145d and 6029a43.

📒 Files selected for processing (1)

• docs/configuration/metric-providers-aws.rst (3 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)

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

🔇 Additional comments (3)

docs/configuration/metric-providers-aws.rst (3)

63-63: Good consolidation of IRSA into a single “Configure Robusta” step

Clearer flow; reduces duplication between earlier steps.

---

75-97: One configuration source of truth: toolset vs env vars

With prometheus/metrics.config present, consider dropping the runner.additional_env_vars (PROMETHEUS_SSL_ENABLED, AWS_SERVICE_NAME, AWS_REGION) to avoid drift. If the chart requires env vars, then remove the duplicated keys from the toolset config instead (as in the patch above). Please confirm which path the Helm chart consumes at runtime.

---

99-99: Step reference check

Ensure the “Simple Upgrade” anchor still renders as the correct target after renumbering (2. Update Robusta).