From 7eb97ad047215a28d476e325e32de6d7ed65b89e Mon Sep 17 00:00:00 2001 From: Markus Napp Date: Mon, 12 Oct 2020 13:05:27 +0200 Subject: [PATCH] Fix anchors for updating and troubleshooting --- adoc/admin-cluster-management.adoc | 8 ++++---- adoc/admin-troubleshooting.adoc | 4 ++-- adoc/admin-updates.adoc | 3 +-- 3 files changed, 7 insertions(+), 8 deletions(-) diff --git a/adoc/admin-cluster-management.adoc b/adoc/admin-cluster-management.adoc index 8b7e7d57f..28b4959b0 100644 --- a/adoc/admin-cluster-management.adoc +++ b/adoc/admin-cluster-management.adoc @@ -19,7 +19,7 @@ from the original management workstation. Bootstrapping the cluster is the initial process of starting up a minimal viable cluster and joining the first master node. Only the first master node needs to be bootstrapped, -later nodes can simply be joined as described in <>. +later nodes can simply be joined as described in <>. Before bootstrapping any nodes to the cluster, you need to create an initial cluster definition folder (initialize the cluster). @@ -28,7 +28,7 @@ This is done using `skuba cluster init` and its `--control-plane` flag. For a step by step guide on how to initialize the cluster, configure updates using `kured` and subsequently bootstrap nodes to it, refer to the _{productname} Deployment Guide_. -[[adding_nodes]] +[#adding-nodes] == Adding Nodes Once you have added the first master node to the cluster using `skuba node bootstrap`, @@ -65,7 +65,7 @@ If you are using a virtual machine template for creating new cluster nodes, you must make sure that *before* joining the cloned machine to the cluster it is updated to the same software versions than the other nodes in the cluster. -Refer to <>. +Refer to <>. Nodes with mismatching package or container software versions might not be fully functional. @@ -129,7 +129,7 @@ you will need to use a combination of commands. . Reinstall the node from scratch. . Run `skuba node join --role --user --sudo --target `. -[[node_operations]] +[#node_operations] == Node Operations === Uncordon and Cordon diff --git a/adoc/admin-troubleshooting.adoc b/adoc/admin-troubleshooting.adoc index c20cc5721..0bb42b787 100644 --- a/adoc/admin-troubleshooting.adoc +++ b/adoc/admin-troubleshooting.adoc @@ -465,8 +465,8 @@ Dex & Gangway will then use the same client secret. == Replacing a Lost Node -If your cluster loses a node, for example due to failed hardware, remove the node as explained in <>. -Then add a new node as described in <>. +If your cluster loses a node, for example due to failed hardware, remove the node as explained in <>. +Then add a new node as described in <>. == Rebooting an Undrained Node with RBD Volumes Mapped diff --git a/adoc/admin-updates.adoc b/adoc/admin-updates.adoc index a14c09fe9..56888e9ee 100644 --- a/adoc/admin-updates.adoc +++ b/adoc/admin-updates.adoc @@ -1,5 +1,4 @@ -[[handling_updates]] - +[#handling_updates] == Update Requirements [IMPORTANT]