K8SPSMDB-1080 - Push failed test k8s logs to S3 bucket

[tplavcic]

CHANGE DESCRIPTION

Notes:

• currently it collects the secrets as well so the logs are pushed to private bucket
• it doesn't use pt-k8s-debug-collector because I didn't like the output of this tool at the time (it collects multiple logs into one file and some of the logs were more machine readable then for humans)
• it prints the bucket location in the github comment so the logs can be copied with a command like aws s3 cp s3://percona-jenkins-artifactory/cloud-psmdb-operator/PR-1324/7a70e0de/logs/ . --recursive

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 the manifests (crd/bundle) regenerated if needed?
• [ ] 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 MongoDB version?
• [ ] Does the change support oldest and newest supported Kubernetes version?

[JNKPercona]

Test name	Status
arbiter	passed
balancer	passed
custom-replset-name	passed
custom-tls	passed
cross-site-sharded	passed
data-at-rest-encryption	passed
data-sharded	passed
demand-backup	passed
demand-backup-eks-credentials	passed
demand-backup-physical	passed
demand-backup-physical-sharded	passed
demand-backup-sharded	passed
expose-sharded	passed
ignore-labels-annotations	passed
init-deploy	passed
finalizer	passed
ldap	passed
ldap-tls	passed
limits	passed
liveness	passed
mongod-major-upgrade	passed
mongod-major-upgrade-sharded	passed
monitoring-2-0	passed
multi-cluster-service	passed
non-voting	passed
one-pod	passed
operator-self-healing-chaos	passed
pitr	passed
pitr-sharded	passed
pitr-physical	passed
pvc-resize	passed
recover-no-primary	passed
rs-shard-migration	passed
scaling	passed
scheduled-backup	passed
security-context	passed
self-healing-chaos	passed
service-per-pod	failure
serviceless-external-nodes	passed
smart-update	passed
split-horizon	passed
storage	passed
tls-issue-cert-manager	passed
upgrade	passed
upgrade-consistency	passed
upgrade-consistency-sharded-tls	passed
upgrade-sharded	passed
users	passed
version-service	passed
We run 49 out of 49

commit: https://github.com/percona/percona-server-mongodb-operator/pull/1324/commits/1338970f3d7ed487d676f996f7ced93ea0d33aed image: perconalab/percona-server-mongodb-operator:PR-1324-1338970f logs: s3://percona-jenkins-artifactory/cloud-psmdb-operator/PR-1324/1338970f/logs/