Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Addons docs #103

Draft
wants to merge 6 commits into
base: newdocs
from

Conversation

@evilnick
Copy link
Contributor

commented Aug 12, 2019

No description provided.

evilnick added some commits Aug 7, 2019

@webteam-app

This comment has been minimized.

microk8s.kubectl -n kube-system edit configmap/coredns
```

This will invoke the `vim` editor so you can alter the configuration.

This comment has been minimized.

Copy link
@evilnick

evilnick Aug 12, 2019

Author Contributor

Is this really the best way to do this? Is there not a kubectl patch command we could give
I fear for people being dumped in vim

This comment has been minimized.

Copy link
@ktsakalozos

ktsakalozos Aug 13, 2019

Contributor

It seems there is a kubectl patch command! https://kubernetes.io/docs/reference/kubectl/cheatsheet/#patching-resources Just saw that.

This comment has been minimized.

Copy link
@ktsakalozos

ktsakalozos Aug 14, 2019

Contributor

Looking into this a bit more it is better to edit this in an editor. The reason is that if we are to provide a patch we would need to craft a string that would re-insert this field: https://github.com/ubuntu/microk8s/blob/master/microk8s-resources/actions/coredns.yaml#L21. This would be a multiline patch with escape characters; very ugly.

Next, you need a connection to the API server. While the MicroK8s snap will have an IP address on your local network, the recommended way to do this is through the proxy service. You can initiate the proxy with the command:

```bash
microk8s.kubectl proxy --accept-hosts=.* --address=0.0.0.0 &

This comment has been minimized.

Copy link
@evilnick

evilnick Aug 12, 2019

Author Contributor

I am assuming that running proxy is the 'approved' method

This comment has been minimized.

Copy link
@ktsakalozos

ktsakalozos Aug 14, 2019

Contributor

Yes this is the recommended way based on the upstream docs https://kubernetes.io/docs/tasks/access-application-cluster/web-ui-dashboard/#accessing-the-dashboard-ui

Note that this process is slightly different when RBAC is enabled. What we currently do is print the following message when the user does a microk8s.enable dashboard:

If RBAC is not enabled access the dashboard using the default token retrieved with:

token=$(microk8s.kubectl -n kube-system get secret | grep default-token | cut -d " " -f1)
microk8s.kubectl -n kube-system describe secret $token

In an RBAC enabled setup (microk8s.enable RBAC) you need to create a user with restricted
permissions as shown in https://github.com/kubernetes/dashboard/wiki/Creating-sample-user

We also got this issue on improving the UX: ubuntu/microk8s#584

We may end-up printing the token as well. Any suggestions are welcomed.

limits:
nvidia.com/gpu: 1
```

This comment has been minimized.

Copy link
@evilnick

evilnick Aug 12, 2019

Author Contributor

I feel there may be some troubleshooting connected to this - I guess we can add a link here

it.

For more information on using this private registry, please see the
[Working with registries documentation](#ref)

This comment has been minimized.

Copy link
@evilnick

evilnick Aug 12, 2019

Author Contributor

We have docs for this, I will update the link when we have the rest in place

evilnick added some commits Aug 13, 2019

@pmahnke pmahnke removed their assignment Aug 16, 2019

@pmahnke pmahnke added the Blocked label Aug 16, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.