# Change PVC access mode for Prometheus/Alertmanager

**URL:** <https://discuss.prometheus.io/t/change-pvc-access-mode-for-prometheus-alertmanager/1400>\
**Category:** Prometheus server\
**Created:** [January 19, 2023, 10:15am UTC](https://discuss.prometheus.io/t/change-pvc-access-mode-for-prometheus-alertmanager/1400 "2023-01-19T10:15:06Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![olti](https://dub1.discourse-cdn.com/flex017/user_avatar/discuss.prometheus.io/olti/32/595_2.png) [@olti](https://discuss.prometheus.io/u/olti)\
**Post date:** [January 19, 2023, 10:15am UTC](https://discuss.prometheus.io/t/change-pvc-access-mode-for-prometheus-alertmanager/1400/1 "2023-01-19T10:15:06Z")

</div>

i am running an AKS cluster and i have deployed Prometheus and Alertmanager via deployment resources in k8s and they also are controlled by replicaset.The issue is that sometimes the restart of Alertmanger get stuck.It is related to `accessMode` of PVC.During restart,k8s will start the new pod in a different node from the currently node where the running pod is assigned,depending on resource utilization on the node.In simple words it means,same PVC is accessed from 2 different pods assigned to different nodes.This is not allowed because in the config of PVC i am using `accessMode ReadWriteOnce`.Looking this [comment](https://github.com/prometheus-operator/prometheus-operator/issues/978#issuecomment-364863367) in github for `prometheus operator` seems to be by design that option `accessMode ReadWriteMany` is not allowed.

So my questions, why such design and what could happen if i change `accessMode` to ` ReadWriteMany`?Any practical experience?