Hi Ali, this is indeed a possible way to do it, use emptyDir first and then reconfigure the right volume;
Le mer. 29 août 2018 à 14:46, Ali Akil <[email protected]> a écrit : > Hi everyone, > > i don't really understand why the [documentation]( > https://docs.okd.io/3.10/install/configuring_inventory_file.html#advanced-install-cluster-logging) > states only 3 options to configure persistent storage for cluster logging > (Option A: Dynamic with glusterfs,Option B: NFS Host Group,Option C: > External NFS Host) and an another part of the [documentation]( > https://docs.okd.io/3.10/install_config/aggregate_logging.html#aggregated-elasticsearch) > states > >Using NFS storage as a volume or a persistent volume (or via NAS such as > Gluster) is not supported for Elasticsearch storage > > The only way remains for me is using a local volume (hostpath) since i > need to preserve the ES-data but the documentation does not state how to > configure this option in the inventory file. Should i use emptydir volumes > then reconfigure the logging after the installation ? > > I want to deploy openshift-origin 3.9 on centos 7.5 with one ES pod. > _______________________________________________ > dev mailing list > [email protected] > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev >
_______________________________________________ dev mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
