[jboss-jira] [JBoss JIRA] (WFWIP-186) PVC access mode is hardcoded to ReadWriteOnce

Jeff Mesnil (Jira) issues at jboss.org
Mon Sep 9 11:44:00 EDT 2019


    [ https://issues.jboss.org/browse/WFWIP-186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13781833#comment-13781833 ] 

Jeff Mesnil commented on WFWIP-186:
-----------------------------------

I think this is not an issue.

It is correct that the PVC for each pod is mounted as ReadWriteOnce since only one pod should access it (PV are not shared between Pods).

I followed Prometheus convention to reuse the PersistentVolumeClaim to configure the PVC but only a subset of the spec is actually used:
* the resources (for requests and limits)
* the selector
I can update the documentation to clarify which part of the PersistentVolumeClaim spec is actually taken into account.

Re `oc edit pvc simple-jaxrs-eap72-volume-simple-jaxrs-eap72-0`, the spec (the desired feature) correctly states that the accessModes is `ReadWriteOnce`, while the status (the actual feature) supports both `ReadWriteOnce` and `ReadWriteMany`

> PVC access mode is hardcoded to ReadWriteOnce
> ---------------------------------------------
>
>                 Key: WFWIP-186
>                 URL: https://issues.jboss.org/browse/WFWIP-186
>             Project: WildFly WIP
>          Issue Type: Bug
>          Components: OpenShift
>            Reporter: Martin Choma
>            Assignee: Jeff Mesnil
>            Priority: Blocker
>
> Setting different access mode (ReadWriteMany, ReadOnlyMany) is ignored 
> [1] https://github.com/wildfly/wildfly-operator/blob/master/pkg/controller/wildflyserver/wildflyserver_controller.go#L404



--
This message was sent by Atlassian Jira
(v7.13.5#713005)


More information about the jboss-jira mailing list