Skip to content

Conversation

FxKu
Copy link
Member

@FxKu FxKu commented Nov 4, 2020

Risizing volumes by updating the PVC storage field has been introduced with #958. However the UPDATE event wasn't covered. Using pvc mode requires more privileges than what we currently list in the operator cluster role. In the helm chart we can arrange the RBAC nicely by checking the storage_resize_mode setting.

This PR also changes the storage_resize_mode in example manifests and charts to pvc. The internal default however remains ebs.

@FxKu FxKu added this to the 1.6 milestone Nov 4, 2020
@FxKu FxKu force-pushed the storage-resize-fixes branch from 898f065 to b4ba102 Compare November 4, 2020 17:07
@sdudoladov
Copy link
Member

the test failure you see in this PR is addressed in #1202

@FxKu FxKu added the zalando label Nov 11, 2020
@sdudoladov
Copy link
Member

👍

1 similar comment
@FxKu
Copy link
Member Author

FxKu commented Nov 11, 2020

👍

@FxKu FxKu merged commit 3fed565 into master Nov 11, 2020
PetterSa pushed a commit to PetterSa/postgres-operator that referenced this pull request Nov 19, 2020
* check resize mode on update events

* add unit test for PVC resizing

* set resize mode to pvc in charts and manifests

* add test for quantityToGigabyte

* just one debug line for syncing volumes

* extend test and update log msg
PetterSa added a commit to PetterSa/postgres-operator that referenced this pull request Nov 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants