open-webui / open-webui/terminals
bug: Resources are not recreated after deletion
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 108
- Forks
- 23
- Avg merge
- 12h 8m
- Merged PRs (30d)
- 1
Description
I've noticed that unclean deletions of resources will result in said resources not being recreated.
So if I have an active session on openwebui and want to use openterminal, it will create a pod which openwebui connects to.
If the pod is deleted (either via a manual deletion through kubectl or if the node where the pod is on dies and restarts) it will not be recreated and openwebui will continue trying to reconnect to that deleted pod.
I was able to "fix" said behavior and will create a PR with the fix and will link it to this issue.
Although I have used claude.ai to fix the problem which should be visible in the commit history.
I unfortunately lack the experience in the python lib that is used and in the exact workings of how the operator and orchestrator works which is why my commit is 100% vibe coded.
I have skimmed over the commit but my lack of experience inhibits my judgement if everything is up to code and 100% logical.
The PR could perhaps be used as a base for a better implementation.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the operator and orchestrator resource lifecycle and reproduce the behavior by deleting a pod through kubectl or simulating node loss. Done means the resource is recreated and OpenWebUI can reconnect, with the implementation reviewed for correctness and covered by the project's existing checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, python
- Domain
- backend, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100