Skip to content

Commit

Permalink
Update faq with server/agent info
Browse files Browse the repository at this point in the history
Signed-off-by: Derek Nola <[email protected]>
  • Loading branch information
dereknola committed Sep 5, 2023
1 parent e3fffe5 commit 9c8f9a0
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 3 deletions.
4 changes: 1 addition & 3 deletions docs/architecture/architecture.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,9 +6,7 @@ weight: 1
import ThemedImage from '@theme/ThemedImage';
import useBaseUrl from '@docusaurus/useBaseUrl';

This page describes the architecture of a high-availability K3s server cluster and how it differs from a single-node server cluster.

It also describes how agent nodes are registered with K3s servers.
### Servers and Agents

* A server node is defined as a host running the `k3s server` command, with control-plane and datastore components managed by K3s.
* An agent node is defined as a host running the `k3s agent` command, without any datastore or control-plane components.
Expand Down
4 changes: 4 additions & 0 deletions docs/faq/faq.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,10 @@ Simply start K3s server with `--disable=traefik` and deploy your ingress.

At this time K3s does not natively support Windows, however we are open to the idea in the future.

### What exactly are Servers and Agents?

For a breakdown on the components that make up a server and agent, see the [Architecture page](../architecture/architecture.md).

### How can I build from source?

Please reference the K3s [BUILDING.md](https://github.com/k3s-io/k3s/blob/master/BUILDING.md) with instructions.
Expand Down

0 comments on commit 9c8f9a0

Please sign in to comment.