KusionStack / KusionStack/kuperator
Enhancement: improvement of pod replace encounters poddecoration changed
Open
@ColdsteelRail is already working on this.
Since Aug 22, 2024.
kind/feature
- Dominant language
- Go
- Stars
- 100
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
What would you like to be added?
Case: pod1 is replaced by pod2, then pod1's pd changed
Now: pd will not be effective until pod1 is replaced succeeded by pod2
Want:
1) pod2 should be deleted
2) create a pod3 with effective pd,
3) delete pod1
Why is this needed?
pd update progress should not be blocked by pod replace
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.
Assessment
This issue has not been assessed yet.