fix tenant labels

[klinch0]

Summary by CodeRabbit

• New Features

  • Updated the HelmRelease configuration for monitoring agents to simplify tenant label assignment by using the release namespace directly.

• Bug Fixes

  • Adjusted the logging configuration for fluent-bit to ensure accurate categorization and processing of monitoring data.

[coderabbitai]

Walkthrough

The changes involve modifications to the HelmRelease configuration for monitoring agents in a Kubernetes environment. Specifically, the variable $targetTenant has been replaced with .Release.Namespace in the vmagent.externalLabels and fluent-bit filter sections. This update simplifies the tenant label assignment by directly using the release namespace instead of a value derived from the namespace annotation. The overall structure, metadata, and dependencies of the HelmRelease remain unchanged.

Changes

File Path	Change Summary
packages/apps/kubernetes/templates/helmreleases/monitoring-agents.yaml	Replaced $targetTenant with .Release.Namespace in vmagent.externalLabels and fluent-bit filter configurations. Structure and dependencies unchanged.

Poem

In the land of code where the rabbits play,
A change was made to brighten the day.
The tenant label now sings with glee,
Using the namespace, as simple as can be!
Hop along, dear friends, let’s celebrate,
For in our HelmRelease, we’ve made it great! 🐰✨

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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

[kvaps]

Shouldn't it be .Release.Name?

[klinch0]

no, release name - is name of HelmRelease (cluster name), like kubernetes-patch12toroot

[klinch0]

tenant - its name of namespace, where HelmRelease

[kvaps]

got it!

[coderabbitai]

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)

packages/apps/kubernetes/templates/helmreleases/monitoring-agents.yaml (1)

Line range hint 1-2: Consider cleaning up unused variables.

If $targetTenant is only used for remoteWrite.url now, and if that usage should also be changed to .Release.Namespace, consider removing the variable declaration and lookup.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 003edf8 and 91871e4.

📒 Files selected for processing (1)

• packages/apps/kubernetes/templates/helmreleases/monitoring-agents.yaml (2 hunks)

🔇 Additional comments (2)

packages/apps/kubernetes/templates/helmreleases/monitoring-agents.yaml (2)

48-48: LGTM! The tenant label changes look good.

The change to use .Release.Namespace for tenant labels in both vmagent and fluent-bit configurations makes the tenant identification more straightforward and consistent.

Also applies to: 100-100

---

Line range hint 51-52: Verify the remoteWrite URL configuration.

The remoteWrite.url still uses $targetTenant while the tenant labels have been changed to use .Release.Namespace. This seems inconsistent with the tenant label changes. Please verify if this URL should also use .Release.Namespace for consistency.

[kvaps]

LGTM