Cannot deploy k8s charm with multiple stores

Thanks for the bug report. This is indeed a bug, but I'd like to understand your use case for this? Just so we can make sure it works as expected in Kubernetes.

That's an excellent question.

Given the fact that metadata.yaml mount points seem to not support multiple stores,

    mounts:
      - storage: database
        location: /var/lib/prometheus

i.e. there is no way to map between mounted location in the workload (/var/lib/prometheus) and mounted locations in the charm container (/var/lib/juju/storage/<name>/<num>), it indeed seems that:

> "Juju does not currently support multiple storage instances for charms using “containers” functionality." [1]

Regardless, I don't think I have a use case at all: prometheus, in this example, does not support splitting its db across multiple volumes.

But this originally came up because I was trying to see if a PVC's capacity could change from one store instance to another. [2]

[1]: https://juju.is/docs/sdk/storage#heading--storage-model
[2]: https://github.com/canonical/prometheus-k8s-operator/pull/295/files

This Medium-priority bug has not been updated in 60 days, so we're marking it Low importance. If you believe this is incorrect, please update the importance.