K8SPG-777 set crVersion

[nmarukovich]

CHANGE DESCRIPTION

Problem:
Add validation for crVersion and ensure it is set if empty.
Since crVersion is defined as a string, we must store it as a string value to avoid validation errors.

// Version is the application version in the format X.Y.Z (e.g., "2.7.0").
	// +kubebuilder:validation:Pattern=`^$|^\d+\.\d+\.\d+$`
	// +kubebuilder:example="2.7.0"
	CRVersion string `json:"crVersion,omitempty"`

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

[github-actions]

[goimports-reviser] _{reported by reviewdog 🐶}

Suggested change

logf "sigs.k8s.io/controller-runtime/pkg/log"

[hors]

Can I use 2.6.0 with this CRD?

[nmarukovich]

yes, it was like en example.
how can we make it better?

[hors]

ok, please check this test https://percona-jenkins-artifactory-public.s3.amazonaws.com/cloud-pg-operator/PR-1210/bf0768457/upgrade-consistency.log

[nmarukovich]

fixed.

[JNKPercona]

Test Name	Result	Time
backup-enable-disable	failure	00:00:00
custom-extensions	passed	00:00:00
custom-tls	passed	00:00:00
demand-backup	passed	00:00:00
finalizers	passed	00:00:00
init-deploy	passed	00:00:00
monitoring	passed	00:00:00
monitoring-pmm3	passed	00:08:29
one-pod	passed	00:00:00
operator-self-healing	passed	00:00:00
pgvector-extension	passed	00:00:00
pitr	passed	00:00:00
scaling	passed	00:00:00
scheduled-backup	passed	00:00:00
self-healing	passed	00:00:00
sidecars	passed	00:00:00
start-from-backup	passed	00:00:00
tablespaces	passed	00:00:00
telemetry-transfer	passed	00:00:00
upgrade-consistency	passed	00:00:00
upgrade-minor	passed	00:00:00
users	passed	00:00:00
We run 22 out of 22		00:08:29

commit: 0b8a9b0
image: perconalab/percona-postgresql-operator:PR-1210-0b8a9b06d