ROB-1409 make sure holmes pod restarts on config changes - #472
Conversation
WalkthroughThe Helm deployment template for the Holmes application was updated to modify the checksum annotation logic. Instead of only using Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant Helm
participant Kubernetes
User->>Helm: Update values (toolsets, modelList, mcp_servers)
Helm->>Kubernetes: Apply deployment with new checksum annotation
Kubernetes->>Kubernetes: Detect checksum change
Kubernetes->>Kubernetes: Trigger pod reload
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 (
|
There was a problem hiding this comment.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
helm/holmes/templates/holmes.yaml(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
- GitHub Check: build (3.12)
Summary by CodeRabbit