MicroK8s services restart after a refresh
See original GitHub issueDue to https://forum.snapcraft.io/t/disabled-snap-gets-enabled-after-a-refresh/7457/8 even if you have done microk8s.stop
microk8s will start again on a refresh.
If pods remain in the Pending state and your node is shown as SchedulingDisabled
in microk8s.kubectl get no
, you will want to do a microk8s.kubectl uncordon "your_node"
.
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
MicroK8s services restart after a refresh · Issue #474 - GitHub
Hi @bjrne , what version of MIcroK8s are you on? Starting with 1.22 the K8s services will restart when refreshing but the workloads...
Read more >Command reference - MicroK8s
microk8s refresh -certs · -c : Check the expiration time of the current certificates. · -e : The certificate to be autogenerated, must...
Read more >Configuring MicroK8s services
To reconfigure a service you will need to edit the corresponding file and then restart MicroK8s. For example, to add debug level logging...
Read more >Troubleshooting - MicroK8s
It is important to recognise that things can go wrong. But MicroK8s gives you tools to help work out what has gone wrong,...
Read more >Services and ports - MicroK8s
After changing, refresh the certificates with: sudo microk8s refresh-certs. This will generate new certs and restart the apiserver. Your DNS server settings ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I am very sorry, I investigated this further and it seems that I missed the
--disable
flag for thesnap stop
command. Since the bug in snap seems to have been fixed, it was probably only my user error that caused microk8s to unwantedly start again. Sorry again for the confusion, this can probably be closed again. I’ll report back in the unlikely case that the problem will appear again.For everyone else who comes here via google:
snap stop --disable microk8s
is probably what you’re looking for if you want to stop microk8s from starting again after a snap refresh or reboot.