K8SPXC-1719: check containerd for chaos install

[eleo007]

CHANGE DESCRIPTION

Problem:
During install of chaos mesh runtime should be specified. We have used default containerd for all the platforms while openshift uses cri-o and minkube uses docker.

Cause:
Short explanation of the root cause of the issue if applicable.

Solution:
Check node rntime before install of chaos mesh.

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?

[JNKPercona]

Test Name	Result	Time
affinity-8-0	passed	00:06:28
auto-tuning-8-0	passed	00:19:09
cross-site-8-0	passed	00:35:48
custom-users-8-0	failure	00:09:20
demand-backup-cloud-8-0	passed	00:55:19
demand-backup-encrypted-with-tls-8-0	passed	00:46:25
demand-backup-8-0	passed	00:43:07
demand-backup-flow-control-8-0	passed	00:11:17
demand-backup-parallel-8-0	passed	00:09:31
demand-backup-without-passwords-8-0	passed	00:16:00
haproxy-5-7	passed	00:16:00
haproxy-8-0	passed	00:14:57
init-deploy-5-7	passed	00:16:57
init-deploy-8-0	passed	00:18:21
limits-8-0	passed	00:12:02
monitoring-2-0-8-0	passed	00:22:54
monitoring-pmm3-8-0	passed	00:18:14
one-pod-5-7	passed	00:14:29
one-pod-8-0	passed	00:13:54
pitr-8-0	passed	00:44:03
pitr-gap-errors-8-0	passed	00:55:54
proxy-protocol-8-0	passed	00:09:29
proxysql-sidecar-res-limits-8-0	passed	00:08:26
pvc-resize-5-7	passed	00:17:41
pvc-resize-8-0	passed	00:17:13
recreate-8-0	passed	00:16:58
restore-to-encrypted-cluster-8-0	passed	00:25:56
scaling-proxysql-8-0	passed	00:08:29
scaling-8-0	passed	00:10:47
scheduled-backup-5-7	passed	01:04:47
scheduled-backup-8-0	passed	01:02:14
security-context-8-0	passed	00:26:26
smart-update1-8-0	passed	00:33:40
smart-update2-8-0	passed	00:39:27
storage-8-0	passed	00:11:09
tls-issue-cert-manager-ref-8-0	passed	00:08:48
tls-issue-cert-manager-8-0	passed	00:11:36
tls-issue-self-8-0	passed	00:13:37
upgrade-consistency-8-0	passed	00:11:24
upgrade-haproxy-5-7	passed	00:24:24
upgrade-haproxy-8-0	passed	00:24:43
upgrade-proxysql-5-7	passed	00:15:39
upgrade-proxysql-8-0	passed	00:15:20
users-5-7	passed	00:24:56
users-8-0	passed	00:25:34
validation-hook-8-0	passed	00:01:50
We run 46 out of 46		17:11:00

commit: c5ade25
image: perconalab/percona-xtradb-cluster-operator:PR-2193-c5ade252