From 697af8e165bf9bdba5d95ce04af1c54c73def79b Mon Sep 17 00:00:00 2001 From: Catherine Luse Date: Tue, 9 Jun 2020 16:24:10 -0700 Subject: [PATCH] Link to details about auto-deployed manifests for K3s --- content/k3s/latest/en/architecture/_index.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/content/k3s/latest/en/architecture/_index.md b/content/k3s/latest/en/architecture/_index.md index 6b116eb62e2..106c2d460c8 100644 --- a/content/k3s/latest/en/architecture/_index.md +++ b/content/k3s/latest/en/architecture/_index.md @@ -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. \ No newline at end of file +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. \ No newline at end of file