Do not create Medusa standalone POD when it's not required

[adziura-tcloud]

What is missing?
Not possible to ignore Medusa standalone deployment creation or configuring existing one (at least I was not able to find it)

Why do we need it?
If we do not need/want to do a restore, additional POD is not necessary to be running.

• K8ssandra Operator version:

  Starting from 1.8.0

[c3-clement]

Today, can restoration be performed without the medusa-standalone pod?

[adejanovski]

Yes, the operator computes the mapping and we have all the information we need in the MedusaBackup objects to compute it without requiring to read anything from the storage bucket.

[adejanovski]

We still have some calls which go through the standalone pod that should instead go through one of the Cassandra pods.

[adziura-tcloud]

@adejanovski , please correct me if I wrong, you want to improve this and it will be possible to omit creation of standalone Medusa deployment in future releases?

another issue, when I upgraded k8ssandra-operator from 1.7.0 to 1.15.0 I noticed that Medusa version in Standalone deployment is 0.20.1 while inside the Cassandra POD the container image version was not updated (still 0.13.4)
is it expected?
UPD: found an issue after double checking operator logs, not relevant anymore