[BUG] fail to use custom configurations for coordinator
Open
stale
- Dominant language
- C++
- Stars
- 3.6k
- Forks
- 468
- Avg merge
- 29m
- Merged PRs (30d)
- 1
Description
**Describe the bug**
The coordinator's resource configuration is hard-coded. Users fail to use custom configurations.
**To Reproduce**
```
import graphscope
session = graphscope.session(
k8s_coordinator_cpu=1)
```
Then use `kubectl` to describe the coordinator pod, the CPU is still the default value(0.5)
**Expected behavior**
The CPU should be 1
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Environment (please complete the following information):**
- GraphScope version: [0.29.0]
- OS: Ubuntu
- Version 22.04
- Kubernetes Version [v1.30.2]
**Additional context**
Add any other context about the problem here.
Contributor guide
Assessment
This issue has not been assessed yet.