# Deployment on Kubernetes cluster "reconciling"

**URL:** <https://forum.mattermost.com/t/deployment-on-kubernetes-cluster-reconciling/14277>\
**Category:** Troubleshooting\
**Created:** [October 19, 2022, 1:24pm UTC](https://forum.mattermost.com/t/deployment-on-kubernetes-cluster-reconciling/14277 "2022-10-19T13:24:40Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![charlieharcum](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/charlieharcum/32/5995_2.png) [@charlieharcum](https://forum.mattermost.com/u/charlieharcum)\
**Post date:** [October 19, 2022, 1:24pm UTC](https://forum.mattermost.com/t/deployment-on-kubernetes-cluster-reconciling/14277/1 "2022-10-19T13:24:40Z")

</div>

**Summary**  
Attempting a test deployment of Mattermost in a clean Kubernetes Cluster

**Steps to reproduce**  
[How can we reproduce the issue (what version are you using?)](https://docs.mattermost.com/guides/deployment.html)  
Walking through the Kubernetes deployment steps in the deployment guide (and have tried separate avenues along the way)

**Expected behavior**  
Expecting mattermost to come up and run

**Observed behavior**  
No matter what I do, I get to the very last step of:  
kubectl apply -n mattermost -f /path to .yaml file

This executes just fine and then when I monitor with:  
kubectl -n mattermost get mm -2

The “STATE” never changes from reconciling. I’ve waited up to an hour before.

Brand new to mattermost so hoping I’m just missing something obvious.

---

<div class="post-metadata">

**Author:** ![deshetti](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/deshetti/32/6520_2.png) [@deshetti](https://forum.mattermost.com/u/deshetti)\
**Post date:** [March 12, 2023, 11:40pm UTC](https://forum.mattermost.com/t/deployment-on-kubernetes-cluster-reconciling/14277/2 "2023-03-12T23:40:29Z")

</div>

@charlieharcum Were you able to find a resolution for this? Running into the same issue.

---

<div class="post-metadata">

**Author:** ![shamim42](https://avatars.discourse-cdn.com/v4/letter/s/cdc98d/32.png) [@shamim42](https://forum.mattermost.com/u/shamim42)\
**Post date:** [January 26, 2024, 6:05am UTC](https://forum.mattermost.com/t/deployment-on-kubernetes-cluster-reconciling/14277/3 "2024-01-26T06:05:56Z")

</div>

I am also facing the same issue. It’s in ‘reconciling’ state for a long time. I am using Kubernetes version 1.26.x.  
How did you resolve the issue @charlieharcum ?

---

<div class="post-metadata">

**Author:** ![charlieharcum](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/charlieharcum/32/5995_2.png) [@charlieharcum](https://forum.mattermost.com/u/charlieharcum)\
**Post date:** [January 26, 2024, 3:58pm UTC](https://forum.mattermost.com/t/deployment-on-kubernetes-cluster-reconciling/14277/4 "2024-01-26T15:58:50Z")

</div>

I realize I never came back to put our resolution. So for us, it turned out we did not have enough storage to accommodate the persistent volume mattermost was trying to create. Believe all we did was adjust the size of the drive it was trying to create in the YAML and also increased storage on our local node and then it came up just fine.