feat: Allow users to configure labels#72
Conversation
Signed-off-by: Brooke Lew <contact@brookelew.com>
WalkthroughThe Bitwarden SDK Server Helm chart templates and values were extended to support optional labeling and annotation of Kubernetes resources. Conditional rendering blocks were added across multiple templates to consume label and annotation configurations, with corresponding new fields introduced in the values file. Changes
🚥 Pre-merge checks | ✅ 1✅ Passed checks (1 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. No actionable comments were generated in the recent review. 🎉 🧹 Recent nitpick comments
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. Comment |
2e21ed8 to
b3e8b6a
Compare
Skarlso
left a comment
There was a problem hiding this comment.
Thanks for the improvement! :)
Problem Statement
Chart lacks a way to configure labels
Related Issue
#71
Proposed Changes
Allow configuring labels for deployed resources
Checklist
git commit --signoffmake testmake reviewableSummary
Adds support for configuring labels and annotations across Helm chart resources. Updates include:
commonLabels,serviceAccount.labels,podLabels,deploymentLabels,podAnnotations,deploymentAnnotations,service.labels, andservice.annotationscommonLabelsin the bitwarden-sdk-server.labels templatedeploymentLabelsandpodLabelsservice.labelsandservice.annotationsserviceAccount.labelsAll changes are backward compatible and only apply when the corresponding values are provided.