# Microk8s cluster stuck after installing OLM 0.14.1

**URL:** <https://discuss.kubernetes.io/t/microk8s-cluster-stuck-after-installing-olm-0-14-1/12094>\
**Category:** microk8s\
**Created:** [July 31, 2020, 4:55pm UTC](https://discuss.kubernetes.io/t/microk8s-cluster-stuck-after-installing-olm-0-14-1/12094 "2020-07-31T16:55:05Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![balchua1](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/balchua1/32/5372_2.png) [@balchua1](https://discuss.kubernetes.io/u/balchua1)\
**Post date:** [July 31, 2020, 10:28pm UTC](https://discuss.kubernetes.io/t/microk8s-cluster-stuck-after-installing-olm-0-14-1/12094/2 "2020-07-31T22:28:09Z")

</div>

OLM requires to have rbac enabled. I remember an issue regarding OLM. Usually namespaces stuck in `Terminating` state is caused by `CRD`s or `Apiservice` which are not deleted.  
If it is ok for you to do `sudo snap remove microk8s` then `sudo snap install microk8s --channel=<the channel> --classic`.

---

_[View the full topic](https://discuss.kubernetes.io/t/microk8s-cluster-stuck-after-installing-olm-0-14-1/12094)._