Release 0.8.0

[eleo007]

CHANGE DESCRIPTION

Problem:
Short explanation of the problem.

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?
• 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
async-ignore-annotations	failure
auto-config	failure
config	failure
config-router	failure
demand-backup	failure
gr-demand-backup	failure
gr-demand-backup-haproxy	failure
gr-finalizer	skipped
gr-haproxy	skipped
gr-ignore-annotations	skipped
gr-init-deploy	skipped
gr-one-pod	skipped
gr-recreate	skipped
gr-scaling	skipped
gr-security-context	skipped
gr-self-healing	skipped
gr-tls-cert-manager	skipped
gr-users	skipped
haproxy	skipped
init-deploy	skipped
limits	skipped
monitoring	skipped
one-pod	skipped
operator-self-healing	skipped
recreate	skipped
scaling	skipped
service-per-pod	skipped
sidecars	skipped
smart-update	skipped
tls-cert-manager	skipped
users	skipped
version-service	skipped
We run 7 out of 32

commit: c07e4dd
image: perconalab/percona-server-mysql-operator:PR-701-c07e4dd7