Conteneurs et Orchestration – Resize PVCs with no downtime
... / Resize PVCs with no downtime
BMPCreated with Sketch.BMPZIPCreated with Sketch.ZIPXLSCreated with Sketch.XLSTXTCreated with Sketch.TXTPPTCreated with Sketch.PPTPNGCreated with Sketch.PNGPDFCreated with Sketch.PDFJPGCreated with Sketch.JPGGIFCreated with Sketch.GIFDOCCreated with Sketch.DOC Error Created with Sketch.
question

Resize PVCs with no downtime

Par
MaxenceH3
Créé le 2018-04-03 00:16:18 (edited on 2024-09-04 12:32:52) dans Conteneurs et Orchestration

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

```