pingcap / pingcap/tidb-operator
Optimization for `CreateOrUpdateConfigMap`
Open
@mianhk is already working on this.
Since Aug 31, 2021.
enhancement
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 540
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 18
Description
Feature Request
Is your feature request related to a problem? Please describe:
Describe the feature you'd like:
During the configmap sync, we do not check if it exists or not but call the CreateOrUpdateConfigMap function directly, which will call API to the kube-apiserver directly during each sync, increase the load of kube-apiserver, and should be optimized.
Describe alternatives you've considered:
Teachability, Documentation, Adoption, Migration Strategy:
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.