feat(deployments): separate db, storage, and reports deployments

[andrewazores]

Fixes #114 #185 #188

Includes #184 #189 #191

[tthvo]

The helm test fail seems related to a timeout waiting for Cryostat main pod to be healthy (i.e. the old set up with 6 containers). Maybe, increase the timeout could help with this test flankiness?

cryostat-helm/ct.yaml

Line 6 in 786beee

helm-extra-args: --timeout=600s

[andrewazores]

I think that's already quite a long timeout - it shouldn't take 10 minutes for things to get ready. Maybe if the network connection for the test runner is slow and it takes a long time to pull the container images, but even then, 10 minutes still seems like a lot.

I say we get #197 integrated and see if that doesn't fix the test reliability. If things are still timing out and we cannot find any other culprit then maybe increasing the timeout is the last resort.

[tthvo]

I think CI needs updating to add --force option to helm or we must wait for #200 .

[tthvo]

I think CI needs updating to add --force option to helm or we must wait for #200 .

Sorry, as per comment #201 (comment), this is not right behaviour of --force in v3. I think we do need to rename the deployment for seamless upgrade (i.e. CI tests this)...