From 499178a041d2a7233bb1082f04ee0ae6f4d295be Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marc=20Sch=C3=B6chlin?= Date: Tue, 3 Sep 2024 13:12:02 +0200 Subject: [PATCH] add warning MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Marc Schöchlin --- docs/guides/configuration-guide/services/kubernetes.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/docs/guides/configuration-guide/services/kubernetes.md b/docs/guides/configuration-guide/services/kubernetes.md index facbd92336..a90c94b858 100644 --- a/docs/guides/configuration-guide/services/kubernetes.md +++ b/docs/guides/configuration-guide/services/kubernetes.md @@ -7,6 +7,13 @@ sidebar_label: Kubernetes The deployment is based on [k3s-ansible](https://github.com/techno-tim/k3s-ansible) and the defaults are configured and described in [099-k3s.yml](https://github.com/osism/defaults/blob/main/all/099-k3s.yml) +:::warning +K3S is currently not installable on nodes that use a layer-3 underlay network by running an FRR +instance on the node itself. The OSISM integration for this scenario is still pending. +Metal-LB either uses ARP for the leader election (which cannot work in principle) or starts its own +FRR instance which conflicts with the FRR instance of the host. +::: + 1. Optional: If you run your environment begind a http proxy, [configure the proxy settings](../proxy.md) 2. The use of more than 3 name servers for the Kubernetes nodes generates a large number of warning messages as only the first three name servers are used. @@ -21,14 +28,13 @@ are configured and described in [099-k3s.yml](https://github.com/osism/defaults/ openssl rand -base64 1024 ``` - 6. Add this token to the secrets file with the name `k3s_token` ``` make ansible_vault_edit FILE=environments/secrets.yml EDITOR= ``` - A example secret: + An example secret: ``` k3s_token: | 9nfWMSnntyozgwATpsxk/5UFRtW4sRfiDUIFH3JtqUr2vLJ+FN3qdUJyaLFMp0oa