K8SPS-716: add .spec.pitr.backupSource.binlogServer to the ps-restore

[pooknull]

https://perconadev.atlassian.net/browse/K8SPS-716

[Copilot]

Pull request overview

This PR updates the ps-operator Helm chart CRDs to extend the PerconaServerMySQLRestore API so PITR restores can carry a binlogServer configuration under .spec.pitr.backupSource.

Changes:

• Added .spec.pitr.backupSource.binlogServer schema to the PerconaServerMySQLRestore CRD (ps-restore).
• Removed the CRD validation that required .spec.pitr.binlogServer when .spec.pitr.enabled is set (in the PerconaServerMySQL CRD).

Comments suppressed due to low confidence (1)

charts/ps-operator/crds/crd.yaml:5267

• The validation that required spec.pitr.binlogServer when spec.pitr.enabled is true was removed. With the remaining rules structured as ... || !has(self.binlogServer) || (...), a user can now set enabled: true without providing any binlogServer config and still pass CRD validation, which is likely to result in an invalid PITR setup at runtime. Consider restoring the requirement (or adjusting the remaining rules so that binlogServer itself is required when enabled, or explicitly documenting/validating an alternative source).

                    x-kubernetes-validations:
                    - message: binlogServer.image is required when pitr is enabled
                      rule: '!(has(self.enabled) && self.enabled) || !has(self.binlogServer)
                        || (has(self.binlogServer.image) && self.binlogServer.image
                        != '''')'

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

Comments suppressed due to low confidence (1)

charts/ps-operator/crds/crd.yaml:5271

• The validation rules here allow pitr.enabled: true with no binlogServer configured (!has(self.binlogServer) short-circuits), but the error messages still state binlogServer.image/size is required when pitr is enabled. This mismatch is confusing for users and makes it look like CRD validation is stricter than it actually is.

                    - message: binlogServer.image is required when pitr is enabled
                      rule: '!(has(self.enabled) && self.enabled) || !has(self.binlogServer)
                        || (has(self.binlogServer.image) && self.binlogServer.image
                        != '''')'
                    - message: binlogServer.size is required when pitr is enabled
                      rule: '!(has(self.enabled) && self.enabled) || !has(self.binlogServer)
                        || (has(self.binlogServer.size) && self.binlogServer.size
                        > 0)'