public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-05-16 10:03:28 +00:00
Code Issues Packages Projects Releases Wiki Activity

Link to details about auto-deployed manifests for K3s

Browse Source
This commit is contained in:
Catherine Luse
2020-06-09 16:24:10 -07:00
parent ef866a7ea7
commit 697af8e165
1 changed files with 6 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/k3s/latest/en/architecture/_index.md
+6 -1
View File
@@ -15,6 +15,7 @@ This page covers the following topics:
- [High-availability K3s server with an external database](#high-availability-k3s-server-with-an-external-db)
- [Fixed registration address for agent nodes](#fixed-registration-address-for-agent-nodes)
- [How agent node registration works](#how-agent-node-registration-works)
- [Automatically deployed manifests](#automatically-deployed-manifests)
# Single-server Setup with an Embedded DB
@@ -51,4 +52,8 @@ Agents will register with the server using the node cluster secret along with a
If the `/etc/rancher/node` directory of an agent is removed, the password file should be recreated for the agent, or the entry removed from the server.
A unique node ID can be appended to the hostname by launching K3s servers or agents using the `--with-node-id` flag.
A unique node ID can be appended to the hostname by launching K3s servers or agents using the `--with-node-id` flag.
# Automatically Deployed Manifests
The [manifests](https://github.com/rancher/k3s/tree/master/manifests) located at the directory path `/var/lib/rancher/k3s/server/manifests` are bundled into the K3s binary at build time.