# Enabling persistence in Mattermost manifest file

**URL:** <https://forum.mattermost.com/t/enabling-persistence-in-mattermost-manifest-file/13218>\
**Category:** Troubleshooting\
**Created:** [April 15, 2022, 12:43pm UTC](https://forum.mattermost.com/t/enabling-persistence-in-mattermost-manifest-file/13218 "2022-04-15T12:43:14Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![lucasjjee](https://avatars.discourse-cdn.com/v4/letter/l/b5e925/32.png) [@lucasjjee](https://forum.mattermost.com/u/lucasjjee)\
**Post date:** [April 15, 2022, 12:43pm UTC](https://forum.mattermost.com/t/enabling-persistence-in-mattermost-manifest-file/13218/1 "2022-04-15T12:43:14Z")

</div>

In the `values.yml` file for the Mattermost Team Edition Helm chart it has configuration for persistence like:

```nohighlight
persistence:
  data:
      enabled: true
      size: 10Gi
      accessMode: ReadWriteOnce
  plugins:
      enabled: true
      size: 1Gi
      accessMode: ReadWriteOnce

```

So with this configuration Longhorn that we’ve deployed will automatically create a file storage. Is this also possible in the Mattermost manifest when I’m using the Mattermost Operator. I don’t see any documentation about this, only focused on external file storage like a S3 bucket. I just need to enable persistence without giving a URL and secret.

I tried to deploy the manifest, but I’m getting errors in the Mattermost Operator that it fails to check Minio instance.