I'm trying to resize persistent volumes of a stateful set.
When I patched the first pvc, I got the following error :
```
Warning VolumeResizeFailed 56s (x9 over 5m15s) external-resizer cinder.csi.openstack.org resize volume ovh-managed-kubernetes-w81jmu-pvc-8b43d388-4f06-47b3-8386-xxxxxxx failed: rpc error: code = Internal desc = Could not resize volume "59b2b553-a2f9-44ff-89b3-xxxxxxxxxxx" to size 5: Expected HTTP response code 202] when accessing [POST https://volume.compute.gra5.cloud.ovh.net/v3/xxxxxxxxxxx/volumes/59b2b553-a2f9-44ff-89b3-xxxxxxxxxxxx/action], but got 406 instead
{"computeFault": {"message": "Version 3.42 is not supported by the API. Minimum is 3.0 and maximum is 3.15.", "code": 406}}
```
Your [guide on persistent volumes resizing says we have to scale to 0 replicas before, but this is just unacceptable as I need my database to stay up and running.
What is the way to get the volume to resize and achieve the following state ?
```
message: Waiting for user to (re-)start a pod to finish file
system resize of volume on node.
status: "True"
type: FileSystemResizePending
```
Conteneurs et Orchestration – Resize PVCs with no downtime
Sujets apparentés
- Kubectl - TLS handshake timeout
5627
18.03.2019 09:07
- Docker registry private
5375
13.10.2016 07:26
- [Auto TLS sur k8s] ClusterIssuer cert-manager pour OVH
4443
18.11.2017 22:45
- Ingress on ports 80/443 for cluster
4193
05.12.2018 14:44
- Kubernetes Metrics
3186
18.11.2019 10:49
- A-t-on une idée des futurs tarifs?
3035
03.04.2019 19:18
- OVH Managed Kubernetes security patches
2911
06.12.2018 10:23
- Kubernetes ingress port 80 & 443
2783
31.12.2018 11:48
- Node Autoscaling / K8s dans une autre région: est-ce que K8s vaut le coup ?
2599
23.01.2020 16:40
- Datastore commun ?
2592
12.10.2016 12:15