feat: add support for extraPVCs

[eminaktas]

This commit introduces the extraPVCs field in CRD, allowing users to attach additional PVC to main container. #2126

CHANGE DESCRIPTION

Problem:
Short explanation of the problem.

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 PXC version?
• Does the change support oldest and newest supported Kubernetes version?

[CLAassistant]

All committers have signed the CLA.

[SiddharthiMishra]

Voting

[egegunes]

hey @eminaktas, since you're still pushing changes, I wonder if this is ready for review?

[eminaktas]

hey @eminaktas, since you're still pushing changes, I wonder if this is ready for review?

Hey @egegunes, yes, it’s ready for review now. While running a few tests, I noticed some issues caused by this change. The recent pushes include improvements and fixes I made while digging into the code for other related work.

[gkech]

we have some thoughts about this implementation, but first let us run a small test to verify this approach.

[egegunes]

we also need to confirm the new field name (extraPVCs) with Peter to see if it's okay.

[eminaktas]

Since you’re the expert on this, I went with what made the most sense to me at the time. I’d really appreciate hearing your thoughts, since you’re the maintainer and have deeper context.

I haven’t looked into it too deeply yet, but one idea we could also explore is supporting volume expansion for the extra volume.

[egegunes]

@gkech could you please play with this to see if it works and feasible?

[JNKPercona]

Test Name	Result	Time
affinity-8-0	failure	00:00:00
auto-tuning-8-0	failure	00:00:00
cross-site-8-0	failure	00:00:00
custom-users-8-0	failure	00:00:00
demand-backup-cloud-8-0	failure	00:00:00
demand-backup-encrypted-with-tls-8-0	failure	00:00:00
demand-backup-8-0	failure	00:00:00
demand-backup-flow-control-8-0	failure	00:00:00
demand-backup-parallel-8-0	failure	00:00:00
demand-backup-without-passwords-8-0	skipped	00:00:00
haproxy-5-7	skipped	00:00:00
haproxy-8-0	skipped	00:00:00
init-deploy-5-7	skipped	00:00:00
init-deploy-8-0	skipped	00:00:00
limits-8-0	skipped	00:00:00
monitoring-2-0-8-0	skipped	00:00:00
monitoring-pmm3-8-0	skipped	00:00:00
one-pod-5-7	skipped	00:00:00
one-pod-8-0	skipped	00:00:00
pitr-8-0	skipped	00:00:00
pitr-gap-errors-8-0	skipped	00:00:00
proxy-protocol-8-0	skipped	00:00:00
proxysql-sidecar-res-limits-8-0	skipped	00:00:00
pvc-resize-5-7	skipped	00:00:00
pvc-resize-8-0	skipped	00:00:00
recreate-8-0	skipped	00:00:00
restore-to-encrypted-cluster-8-0	skipped	00:00:00
scaling-proxysql-8-0	skipped	00:00:00
scaling-8-0	skipped	00:00:00
scheduled-backup-5-7	skipped	00:00:00
scheduled-backup-8-0	skipped	00:00:00
security-context-8-0	skipped	00:00:00
smart-update1-8-0	skipped	00:00:00
smart-update2-8-0	skipped	00:00:00
storage-8-0	skipped	00:00:00
tls-issue-cert-manager-ref-8-0	skipped	00:00:00
tls-issue-cert-manager-8-0	skipped	00:00:00
tls-issue-self-8-0	skipped	00:00:00
upgrade-consistency-8-0	skipped	00:00:00
upgrade-haproxy-5-7	skipped	00:00:00
upgrade-haproxy-8-0	skipped	00:00:00
upgrade-proxysql-5-7	skipped	00:00:00
upgrade-proxysql-8-0	skipped	00:00:00
users-5-7	skipped	00:00:00
users-8-0	skipped	00:00:00
validation-hook-8-0	skipped	00:00:00
We run 9 out of 46		N/A

commit: 2b1a171
image: perconalab/percona-xtradb-cluster-operator:PR-2128-2b1a1710