In Greenwave, we have two pods. One is for the frontend, the other one is for the backend. Both are caching data. Is is possible to have a persistent volume that can be shared between those two pods in Openshift? So that both of them can read/write the cache data at the same place. I guess this is pretty much what I want to achieve here.
https://docs.openshift.org/latest/install_config/storage_examples/shared_storage.html
@mjia is there anything stopping us from just adding the PersistentVolume and PersistentVolumeClaim definition into the application role, alongside all the rest of the stuff?
Is the issue that we need special permissions to do that?
Or is it that the storage doesn't actually exist right now?
A current explicit limitation of our openshift setup is that none of it has anything persistent, which is why the databases are external. The problem is that we don't have a storage backend that openshift can use. If you need persistent storage, we need to move your app out of openshift.
This is documented on https://fedoraproject.org/wiki/Infrastructure/OpenShift:
6. Storage? NFS? gluster? Initial deployment will be local storage only which will limit our applications to be stateless at the start or be statefulsets that are restricted to a single node (which is not ideal). Storage backends will be evaluated later once we are able to sort out some aspects of the limitation of Fedora Infrastructure's storage network.
Maybe we can run with https://src.fedoraproject.org/container/memcached instead?
OK - we have a workaround for greenwave. I guess we can close this as WONTFIX for now? No need for limbo tickets to hang around. ;)
Metadata Update from @ralph: - Issue close_status updated to: Will Not/Can Not fix - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.