[FEATURE] #1280
Description
📋 Prerequisites
- I have searched the existing issues to avoid creating a duplicate
- By submitting this issue, you agree to follow our Code of Conduct
📝 Feature Summary
The tools in the current McpServer will be bound to the Agent. It is hoped that after the McpServer is upgraded, the relevant agents can complete the active restart. Otherwise, when I call the Agent to ask questions, the message "Session terminated" will appear
❓ Problem Statement / Motivation
What problem does this feature solve?
The tools in the current McpServer are bound to the Agent. Without this feature, the related Agents cannot restart automatically after the McpServer is upgraded, which causes the Session terminated error when invoking the Agent to ask questions.
Why is it important?
This feature ensures that Agents can restart actively after McpServer upgrades, avoiding session termination and service interruption. It stabilizes the interaction between McpServer and Agents, and provides a reliable user experience without unexpected errors.
Who would benefit?
Developers who maintain and upgrade McpServer
Users who invoke Agents for queries and tool calls
Teams relying on stable McpServer-Agent interaction
💡 Proposed Solution
the Agent controller watches for updates to the McpServer CR.
When the McpServer is upgraded, the controller automatically updates an annotation on the related Agent CR.
This annotation change triggers Kubernetes to restart the Agent Pods,preventing the "Session terminated" error.
🔄 Alternatives Considered
No response
🎯 Affected Service(s)
None
📚 Additional Context
No response
🙋 Are you willing to contribute?
- I am willing to submit a PR for this feature