K8SPS-400: custom options for xtrabackup, xbstream, xbcloud

[pooknull]

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

DESCRIPTION

Problem:
In our backups and restoration process we rely on xtrabackup, xbstream and xbcloud. Not always default options for these tools are optimal.

Solution:
Add containerOptions section to ps-backup, ps-restore and ps resources.

containerOptions:
  env:
  - name: VERIFY_TLS
    value: "false"
  - name: XB_USE_MEMORY
    value: "2GB"
  args:
    xtrabackup:
    - "--someflag=abc"
    - "--someotherflag=def"
    xbcloud:
    - "--someflag=abc"
    - "--someotherflag=def"
    xbstream:
    - "--someflag=abc"
    - "--someotherflag=def"

If containerOptions specified in both ps-backup/ps-restore and ps, values from ps-backup/ps-restore will be used.

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

[JNKPercona]

Test name	Status
version-service	passed
async-ignore-annotations	passed
auto-config	passed
config	passed
config-router	passed
demand-backup	passed
async-data-at-rest-encryption	passed
gr-data-at-rest-encryption	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
storage	passed
tls-cert-manager	passed
users	passed
pvc-resize	passed
We run 38 out of 38

commit: fb6e2fa
image: perconalab/percona-server-mysql-operator:PR-986-fb6e2fa0

[hors]

@pooknull please add e2e test for it