EVEREST-1814 add creating state

[oksana-grishchenko]

Add "Creating" DB status

Problem:
EVEREST-1814

Problem:
The DB can be in an ‘unknown’ state for a couple of seconds and we didn't want to show that to the user.

Solution:

The upstream operators have the different statuses when a cluster is being created:

• pxc - "unknown"
• psmdb - ""
• pg does not have any empty status.

So the upstream statuses are different although Everest maps the DB status to the upstream cluster status 1:1. There is no point so far to create a separate mapping for each upstream operator only because we want to unify AppStateCreating, so in this PR the Everest operator unifies the "" and "unknown" statuses into the "creating" status.

Related PRs:

• EVEREST-1714 DB Creating status everest#1084

CHECKLIST

Helm chart

• Is the helm chart updated with the new changes? (if applicable)

Jira

• Is the Jira ticket created and referenced properly?

Tests

• Is an Integration test/test case added for the new feature/change?
• Are unit tests added where appropriate?

[mayankshah1607]

should we remove this since it is not used anywhere now?

[maxkondr]

in addition - is AppStateNew used somehow? and shall it be replaced with AppStateCreating as well?

[oksana-grishchenko]

The way we map statuses now is everestv1alpha1.AppState(upstream.Status.State) which means we still need both

AppStateUnknown AppState = "unknown"
AppStateNew AppState = ""

because pxc has "unknown", psmdb has "", pg does not have any empty status.

As an alternative we could remove the statuses^ and have a switch mapping in each provider separately. I thought it's not really needed right now because the other statuses are mapping 1:1. Do you think it would be better to have the mapping for each upstream operator? I agree it's a bit confusing to have the statuses that are used only internally, but not sure which option would be better here.