K8SPSMDB-1139 handle PVC resize when G unit is used

[gkech]

Jira: https://perconadev.atlassian.net/browse/K8SPSMDB-1139

CHANGE DESCRIPTION

Problem:

All our officially supported platforms (EKS, GKE and AKS) configures PVCs using Gi. But platforms like k3d has a different behavior and on-prem Kubernetes installations can have this behavior too.

Cause:
Short explanation of the root cause of the issue if applicable.

Solution:
Short explanation of the solution we are providing with this PR.

CHECKLIST

Jira

• Is the Jira ticket created and referenced properly?
• Does the Jira ticket have the proper statuses for documentation (Needs Doc) and QA (Needs QA)?
• Does the Jira ticket link to the proper milestone (Fix Version field)?

Tests

• Is an E2E test/test case added for the new feature/change?
• Are unit tests added where appropriate?
• Are OpenShift compare files changed for E2E tests (compare/*-oc.yml)?

Config/Logging/Testability

• Are all needed new/changed options added to default YAML files?
• Are all needed new/changed options added to the Helm Chart?
• Did we add proper logging messages for operator actions?
• Did we ensure compatibility with the previous version or cluster upgrade process?
• Does the change support oldest and newest supported MongoDB version?
• Does the change support oldest and newest supported Kubernetes version?

[JNKPercona]

Test Name	Result	Time
arbiter	passed	00:10:58
balancer	passed	00:17:56
cross-site-sharded	passed	00:19:04
custom-replset-name	passed	00:10:26
custom-tls	passed	00:14:03
custom-users-roles	passed	00:10:23
custom-users-roles-sharded	passed	00:12:00
data-at-rest-encryption	passed	00:13:13
data-sharded	passed	00:23:28
demand-backup	passed	00:16:27
demand-backup-eks-credentials-irsa	passed	00:00:08
demand-backup-fs	passed	00:23:13
demand-backup-if-unhealthy	passed	00:08:36
demand-backup-incremental-aws	passed	00:11:05
demand-backup-incremental-azure	passed	00:10:52
demand-backup-incremental-gcp-native	passed	00:11:55
demand-backup-incremental-gcp-s3	passed	00:10:47
demand-backup-incremental-minio	passed	00:25:35
demand-backup-incremental-sharded-aws	passed	00:18:23
demand-backup-incremental-sharded-azure	passed	00:17:04
demand-backup-incremental-sharded-gcp-native	passed	00:18:06
demand-backup-incremental-sharded-gcp-s3	passed	00:17:49
demand-backup-incremental-sharded-minio	passed	00:27:32
demand-backup-logical-minio-native-tls	passed	00:08:50
demand-backup-physical-parallel	passed	00:08:28
demand-backup-physical-aws	passed	00:11:59
demand-backup-physical-azure	passed	00:11:25
demand-backup-physical-gcp-s3	passed	00:11:50
demand-backup-physical-gcp-native	passed	00:11:38
demand-backup-physical-minio	passed	00:21:38
demand-backup-physical-minio-native	passed	00:26:01
demand-backup-physical-minio-native-tls	passed	00:19:16
demand-backup-physical-sharded-parallel	passed	00:10:36
demand-backup-physical-sharded-aws	passed	00:17:27
demand-backup-physical-sharded-azure	passed	00:17:57
demand-backup-physical-sharded-gcp-native	passed	00:18:41
demand-backup-physical-sharded-minio	passed	00:18:02
demand-backup-physical-sharded-minio-native	passed	00:17:56
demand-backup-sharded	passed	00:26:23
demand-backup-snapshot	passed	00:39:32
demand-backup-snapshot-vault	passed	00:19:24
disabled-auth	passed	00:17:11
expose-sharded	passed	00:34:17
finalizer	passed	00:10:13
ignore-labels-annotations	passed	00:07:46
init-deploy	passed	00:13:14
ldap	passed	00:09:03
ldap-tls	passed	00:12:45
limits	passed	00:06:33
liveness	passed	00:08:53
mongod-major-upgrade	passed	00:12:18
mongod-major-upgrade-sharded	passed	00:21:49
monitoring-2-0	passed	00:25:33
monitoring-pmm3	passed	00:29:33
multi-cluster-service	passed	00:11:19
multi-storage	passed	00:18:55
non-voting-and-hidden	passed	00:17:43
one-pod	passed	00:09:01
operator-self-healing-chaos	passed	00:13:03
pitr	passed	00:33:14
pitr-physical	passed	00:59:37
pitr-sharded	passed	00:21:10
pitr-to-new-cluster	passed	00:25:37
pitr-physical-backup-source	passed	00:54:19
preinit-updates	passed	00:05:08
pvc-auto-resize	passed	00:14:26
pvc-resize	passed	00:16:56
recover-no-primary	passed	00:27:24
replset-overrides	passed	00:19:03
replset-remapping	passed	00:17:19
replset-remapping-sharded	passed	00:17:34
rs-shard-migration	passed	00:14:30
scaling	passed	00:11:37
scheduled-backup	passed	00:18:04
security-context	passed	00:07:08
self-healing-chaos	passed	00:15:42
service-per-pod	passed	00:19:21
serviceless-external-nodes	passed	00:07:25
smart-update	passed	00:08:29
split-horizon	passed	00:14:03
stable-resource-version	passed	00:04:49
storage	passed	00:07:23
tls-issue-cert-manager	passed	00:29:57
unsafe-psa	passed	00:06:36
upgrade	passed	00:10:20
upgrade-consistency	passed	00:06:51
upgrade-consistency-sharded-tls	passed	00:53:03
upgrade-sharded	passed	00:19:41
upgrade-partial-backup	passed	00:16:39
users	passed	00:17:51
users-vault	passed	00:13:17
version-service	passed	00:25:37

Summary	Value
Tests Run	92/92
Job Duration	02:50:14
Total Test Time	26:26:12

commit: d6868af
image: perconalab/percona-server-mongodb-operator:PR-2331-d6868af1c

[egegunes]

@pooknull should we remove rounding logic here like we did in PXC?

[pooknull]

Yes we should. But have done it in this PR: #2341