Hi. On 17 April 2018 at 12:17, Tim Dudgeon <[email protected]> wrote:
> So if you are using dynamic provisioning the only option for logging is > for the default StorageClass to be set to what is needed? > > On 17/04/18 11:12, Per Carlson wrote: > > This holds at least for 3.7: > > For metrics you can use "openshift_metrics_cassanda_pvc_storage_class_name" > (https://github.com/openshift/openshift-ansible/blob/ > release-3.7/roles/openshift_metrics/tasks/generate_cassandra_pvcs.yaml#L44 > ). > > Using a StorageClass for logging (ElasticSearch) is more confusing. The > variable is "openshift_logging_elasticsearch_pvc_storage_class_name" ( > https://github.com/openshift/openshift-ansible/blob/ > release-3.7/roles/openshift_logging_elasticsearch/defaults/main.yml#L34). > But, it is only used for non-dynamic PVCs (https://github.com/openshift/ > openshift-ansible/blob/release-3.7/roles/openshift_ > logging_elasticsearch/tasks/main.yaml#L368-L370). > > > -- > Pelle > > Research is what I'm doing when I don't know what I'm doing. > - Wernher von Braun > > > No, I think you can use a StorageClass by keeping "openshift_logging_elasticsearch_pvc_dynamic" is false. Not sure if that has any side effects though. -- Pelle
_______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
