KusionStack / KusionStack/kuperator
容器发布流程优化
Open
Nobody has claimed this yet.
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?
容器发布时，希望先部署新的容器，再去掉旧的容器
Why is this needed?
目前先去掉容器，节点较少的情况下，对剩下节点压力比较大
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 repository's container release workflow and its Kubernetes resource handling; the issue does not name a file or test. Confirm how old containers are currently removed, then define completion as deploying new containers before removing old ones while avoiding excess pressure on nodes in a small-node deployment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100