Skip to content

Commit

Permalink
Update pre-reqs in ToC
Browse files Browse the repository at this point in the history
Signed-off-by: Alex Ellis (OpenFaaS Ltd) <[email protected]>
  • Loading branch information
alexellis committed Jul 17, 2021
1 parent 89d15f2 commit 4c0bbd5
Showing 1 changed file with 5 additions and 1 deletion.
6 changes: 5 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,7 @@ Status](https://travis-ci.com/alexellis/k3sup.svg?branch=master)](https://travis
- [Demo πŸ“Ό](#demo-)
- [Who is the author? πŸ‘](#who-is-the-author-)
- [Usage βœ…](#usage-)
- [Pre-requisites for k3sup agents and servers](#pre-requisites-for-k3sup-servers-and-agents)
- [πŸ‘‘ Setup a Kubernetes *server* with `k3sup`](#-setup-a-kubernetes-server-with-k3sup)
- [Advanced KUBECONFIG options](#merging-clusters-into-your-kubeconfig)
- [😸 Join some agents to your Kubernetes server](#-join-some-agents-to-your-kubernetes-server)
Expand Down Expand Up @@ -121,6 +122,8 @@ alex ALL=(ALL) NOPASSWD: ALL

In most circumstances, cloud images for Ubuntu and other distributions will not require this step.

As an alternative, if you only need a single server you can log in interactively and run `k3sup install --local` instead of using SSH.

### πŸ‘‘ Setup a Kubernetes *server* with `k3sup`

You can setup a server and stop here, or go on to use the `join` command to add some "agents" aka `nodes` or `workers` into the cluster to expand its compute capacity.
Expand Down Expand Up @@ -607,7 +610,8 @@ Rancher provides support for K3s [on their Slack](https://slack.rancher.io/) in
Common issues:
* Raspberry Pi - you haven't updated cmdline.txt to enable cgroups for CPU and memory
* `sudo: a terminal is required to read the password` - you must either configure your user to have access to sudo without a password, or use the pre-requisites at the top of this file.
* `sudo: a terminal is required to read the password` - see the [Pre-requisites for k3sup agents and servers](#pre-requisites-for-k3sup-servers-and-agents)
* K3s server didn't start. Log in and run `sudo systemctl -u k3s`
* The K3s agent didn't start. Log in and run `sudo systemctl -u k3s-agent`
* You tried to remove and re-add a server in an etcd cluster and it failed. This is a known issue, see the [K3s issue tracker](https://github.com/k3s-io/k3s/issues).
Expand Down

0 comments on commit 4c0bbd5

Please sign in to comment.