Ability to get the related pod label name via an environment variable.#457
Conversation
WalkthroughThe Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~7 minutes Note ⚡️ Unit Test Generation is now available in beta!Learn more here, or try it out under "Finishing Touches" below. 📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🔇 Additional comments (3)
✨ Finishing Touches
🧪 Generate unit tests
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed 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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
This PR adds the ability to specify the KRR_RELATED_POD_LABEL environment variable to provide the name of the label to use to discover a K8S object related pods. The default behavior, if this env variable is not set, is to use
podas before.This is helpful for example when the
honor_labelssetting in Prometheus is set tofalse(the default value) and there is a conflict between labels that are being scraped and labels that Prometheus attaches.See documentation here: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#scrape_config
This can result in the metrics using the label
exported_podinstead ofpod.