K8SPS 388 small refactor on InitContainer, reuse it when needed - e2e test introduction for the case

[gkech]

In this PR we followup on #806 and we add some small refactors to increase maintainability.

Resource Quotas yaml used for testing:

apiVersion: v1
kind: ResourceQuota
metadata:
  name: resource-quota-kech
spec:
  hard:
    requests.cpu: "10"
    requests.memory: "16Gi"
    limits.cpu: "20"
    limits.memory: "32Gi"

Tested the following 2 scenarios:

• spec.mysql.clusterType: group-replication
• spec.mysql.clusterType: async

Resources testing:

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?

Config/Logging/Testability

• Are all needed new/changed options added to default YAML files?
• 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 PS version?
• Does the change support oldest and newest supported Kubernetes version?

[CLAassistant]

All committers have signed the CLA.

[gkech]

removed this since it wasn't used anywhere in the codebase.

[gkech]

Numbers according to : https://docs.percona.com/percona-operator-for-mysql/ps/System-Requirements.html#supported-platforms

[gkech]

Increased memory in order to address some errors as reported here: https://percona-jenkins-artifactory-public.s3.amazonaws.com/cloud-ps-operator/PR-811/21e66a83/init-deploy.log

e.g.

    logger.go:42: 18:50:03 | init-deploy | 2025-01-24 18:43:39 +0000 UTC	Warning	StatefulSet.apps init-deploy-orc		FailedCreate	create Pod init-deploy-orc-1 in StatefulSet init-deploy-orc failed error: pods "init-deploy-orc-1" is forbidden: exceeded quota: init-deploy-resource-quota, requested: limits.memory=1Gi, used: limits.memory=2560Mi, limited: limits.memory=3Gi	statefulset-controller	

[gkech]

commit: 7c64521

[JNKPercona]

Test name	Status
version-service	passed
async-ignore-annotations	passed
auto-config	passed
config	passed
config-router	passed
demand-backup	passed
gr-demand-backup	passed
gr-demand-backup-haproxy	passed
gr-finalizer	passed
gr-haproxy	passed
gr-ignore-annotations	passed
gr-init-deploy	passed
gr-one-pod	passed
gr-recreate	passed
gr-scaling	passed
gr-scheduled-backup	passed
gr-security-context	passed
gr-self-healing	passed
gr-tls-cert-manager	passed
gr-users	passed
haproxy	passed
init-deploy	passed
limits	passed
monitoring	passed
one-pod	passed
operator-self-healing	passed
recreate	passed
scaling	passed
scheduled-backup	passed
service-per-pod	passed
sidecars	passed
smart-update	passed
tls-cert-manager	passed
users	passed
We run 34 out of 34

commit: 8a96dcd
image: perconalab/percona-server-mysql-operator:PR-811-8a96dcd8