Closed wnxn closed 4 years ago
Container | Version | CPU(m) | Memory(MiB) |
---|---|---|---|
provisioner | v1.4.0 | 1 | 12 |
attacher | v1.2.1 | 30 | 20 |
snapshotter | v1.2.2 | 1 | 7 |
resizer | v0.2.0 | 1 | 10 |
csi-qingcloud(controller) | v1.1.0-rc.3 | 1 | 12 |
node-driver-registrar | v1.2.0 | 1 | 4 |
csi-qingcloud(node) | v1.1.0-rc.3 | 1 | 8 |
What happened: In QingCloud CSI v1.1.0, we planed to add Guarantee class of QoS #123 and limited containers' resource request. In KS 2.1 testing, the external-controller container can't start in large cluster. After turning up resource limit and request, the external-controller could run normally.
What you expected to happen: Add more resource in resource limit and request in QingCloud CSI YAML file
How to reproduce it (as minimally and precisely as possible): Deploy QingCloud CSI v1.1.0-rc.3 in 200+ nodes Kubernetes v1.15 cluster
Anything else we need to know?:
Environment:
kubectl version
): v1.15cat /etc/os-release
):uname -a
):