feat: upgrade atlantis and github actions runner controller

[sergs-pci]

Description of the Change

Upgrade two core components

Summary by CodeRabbit

• New Features

  • Added Prometheus scraping annotations to the actions-runner-controller for improved monitoring.

• Chores

  • Upgraded Atlantis and actions-runner-controller to newer Helm chart versions.
  • Updated related metadata labels for both services.
  • Adjusted metrics configuration for actions-runner-controller.

[sergs-pci]

@coderabbitai full review

[coderabbitai]

✅ Actions performed

Full review triggered.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The updates involve upgrading Helm chart versions for the Atlantis and actions-runner-controller applications in their respective Kubernetes ArgoCD manifests. Metadata labels were updated to reflect new versions, and Prometheus scraping annotations were added for actions-runner-controller. The metrics configuration for actions-runner-controller was also adjusted.

Changes

Files	Change Summary
.../core-services/components/atlantis/application.yaml	Upgraded Helm chart version from 4.15.3 to 5.4.2; updated metadata labels to match new chart and app versions.
.../core-services/components/runners/github/actions-runner-controller/application.yaml	Upgraded chart version from 0.20.2 to 0.23.7; updated metadata labels; added Prometheus scrape annotations; changed metrics.serviceMonitor config.

Poem

A hop, a leap, a version bump—
Atlantis sails on a newer pump.
Runners now with metrics bright,
Prometheus scrapes through day and night.
Helm charts rise, the labels sing,
In YAML fields, fresh changes spring!
🐇✨

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 583d82e and 7b396c7.

📒 Files selected for processing (2)

• platform/gitops-pipelines/delivery/clusters/cc-cluster/core-services/components/atlantis/application.yaml (2 hunks)
• platform/gitops-pipelines/delivery/clusters/cc-cluster/core-services/components/runners/github/actions-runner-controller/application.yaml (3 hunks)

---

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