microk8s.kubectl requires sudo
See original GitHub issue$ snap info microk8s
installed: v1.15.3 (778) 171MB classic
$ microk8s.kubectl
You do not have enough permissions to access MicroK8s. Please try again with sudo.
I noticed in the beta that microk8s.kubectl
requires sudo (possibility related to #590).
Is there a way to add a user to a group or something so that they don’t need to type sudo constantly?
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
microk8s.kubectl requires sudo · Issue #606 - GitHub
I noticed in the beta that microk8s.kubectl requires sudo (possibility related to #590). Is there a way to add a user to a...
Read more >Microk8s sudo requirements - CircleCI Discuss
With the upcoming v1.15.3 release, MicroK8s commands will require the use of sudo whenever elevated privileges are needed. For example, microk8s ...
Read more >Get started - MicroK8s
MicroK8s will install a minimal, lightweight Kubernetes you can run and use on practically any machine. It can be installed with a snap:...
Read more >Working with kubectl - MicroK8s
MicroK8s is the simplest production-grade upstream K8s. Lightweight and focused. Single command install on Linux, Windows and macOS.
Read more >Command reference - MicroK8s
Retrieves and outputs the current config information from MicroK8s (similar to that returned by kubectl ). Examples: microk8s config.
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
After updating, I now get this message
I was able to resolve this issue by adding myself to the microk8s group, as suggested by the error message.
There is no specific group. In https://github.com/ubuntu/microk8s/blob/feature/dev-docs/docs/access-without-sudo.md you can see a few methods to work around the sudo requirement including one that lets you permit your user/group to access critical files.