# Microk8s.reset... not resetting - fails

**URL:** <https://discuss.kubernetes.io/t/microk8s-reset-not-resetting-fails/17289>\
**Category:** microk8s\
**Created:** [September 1, 2021, 10:27pm UTC](https://discuss.kubernetes.io/t/microk8s-reset-not-resetting-fails/17289 "2021-09-01T22:27:58Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Alessandro\_Dentella](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/alessandro_dentella/32/6541_2.png) [@Alessandro\_Dentella](https://discuss.kubernetes.io/u/Alessandro_Dentella)\
**Post date:** [September 1, 2021, 10:27pm UTC](https://discuss.kubernetes.io/t/microk8s-reset-not-resetting-fails/17289/1 "2021-09-01T22:27:58Z")

</div>

Hi,  
I’m playing with microk8s with a 2 nodes test micro cluster. It’s my playground so I decided to `microk8s.reset` but the result is that after disabling all addons if fails:

```auto
...
Disabling addon : traefik
Waiting for kubernetes resources to be released
All addons disabled.
Deleting CNI
error when deleting "/var/snap/microk8s/2346/args/cni-network/cni.yaml": Delete "https://127.0.0.1:16443/api/v1/namespaces/kube-system/configmaps/calico-config": dial tcp 127.0.0.1:16443: connect: connection refused
... [repeated several times]

```

As I wasn’t able to reach k8s I rebooted the machine and microk8s get reachable again, but many pods and configuration are still there, i.e. reset has not completed.

The same thing happens if I reset again.

What I wrong in what I’m doing? This node was previously in a 2 node cluster but I used `microk8s.leave` on the other node and `microk8s.remove-node` in this.

Any hint is appreciated  
sandro  
\*🙂

---

<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:** [September 1, 2021, 11:16pm UTC](https://discuss.kubernetes.io/t/microk8s-reset-not-resetting-fails/17289/2 "2021-09-01T23:16:34Z")

</div>

I normally do `snap remove microk8s --purge` followed by `snap install microk8s --classic --channel 1.22`

---

<div class="post-metadata">

**Author:** ![Alessandro\_Dentella](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/alessandro_dentella/32/6541_2.png) [@Alessandro\_Dentella](https://discuss.kubernetes.io/u/Alessandro_Dentella)\
**Post date:** [September 2, 2021, 9:41am UTC](https://discuss.kubernetes.io/t/microk8s-reset-not-resetting-fails/17289/3 "2021-09-02T09:41:04Z")

</div>

Thanks @balchua1,

> [@balchua1](#):
>
> I normally do `snap remove microk8s --purge` followed by `snap install microk8s --classic --channel 1.22`

That works in fact. My understanding is that `microk8s reset` is meant to bypass the need for a new installation.