KusionStack / KusionStack/kuperator
Enhancement: when enableOpsLifecycle, target can be deleted and succeess
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 100
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
What would you like to be added?
If operationjob enableOpsLifecyle when register action, it expects target pod not to be deleted before target operation succeess, otherwise it will be failed.
Why is this needed?
In some cases, users want use lifecycle for operation, and expect to delete pod finally.
So that operationjob should not failed, but success.
Contributor guide
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 operationjob register action when enableOpsLifecycle is enabled, focusing on how deletion of the target pod affects operation success. Reproduce the case where the target pod is deleted before the operation succeeds, then define completion as successful when the lifecycle intentionally deletes the pod.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100