[BUG] Agent deletion leaves orphaned database records #1175
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
- I am using the latest version of the software
- I have tried to clear cache/cookies or used incognito mode (if ui-related)
- I can consistently reproduce this issue
🎯 Affected Service(s)
Controller Service
🚦 Impact/Severity
No impact (Default)
🐛 Bug Description
When an Agent CRD is deleted from Kubernetes, the corresponding database record is not (soft) deleted due to an ID format mismatch between the store and delete operations.
🔄 Steps To Reproduce
- Create an agent
- Delete the agent
- See the agent record still contains deleted_at=null
🤔 Expected Behavior
Deleting an agent will populate the deleted_at column.
📱 Actual Behavior
The agent database record remains untouched.
💻 Environment
No response
🔧 CLI Bug Report
No response
🔍 Additional Context
No response
📋 Logs
📷 Screenshots
No response
🙋 Are you willing to contribute?
- I am willing to submit a PR to fix this issue