chore: Add annotations field to service configuration#173
Merged
Conversation
robodev-r2d2
approved these changes
Nov 27, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request introduces support for custom Kubernetes service annotations for the backend service in the RAG infrastructure Helm chart. The main changes add the ability to specify service annotations via values, making deployments more flexible and customizable.
Helm templating improvements:
service.yamlto conditionally include theannotationsfield for the backend service if specified in values, using Helm templating withtoYamlandnindentfor proper formatting.Configuration enhancements:
annotationsmap to thebackend.servicesection invalues.yaml, allowing users to define service annotations for the backend.