docs: Update doctoc

Also fixes a couple of indendation issues it revealed.

Author: mdbooth

docs/book/src/SUMMARY.md

@@ -10,5 +10,6 @@
     - [CRD Changes](./topics/crd-changes/index.md)
         - [v1alpha4 to v1alpha5](./topics/crd-changes/v1alpha4-to-v1alpha5.md)
         - [v1alpha5 to v1alpha6](./topics/crd-changes/v1alpha5-to-v1alpha6.md)
+        - [v1alpha6 to v1alpha7](./topics/crd-changes/v1alpha6-to-v1alpha7.md)
 - [Development](./development/development.md)
 - [Hacking CI](./development/ci.md)

docs/book/src/clusteropenstack/configuration.md

@@ -5,6 +5,8 @@
 - [Required configuration](#required-configuration)
   - [OpenStack version](#openstack-version)
   - [Operating system image](#operating-system-image)
+    - [cloud-init based images](#cloud-init-based-images)
+    - [Ignition based images](#ignition-based-images)
   - [SSH key pair](#ssh-key-pair)
   - [OpenStack credential](#openstack-credential)
     - [Generate credentials](#generate-credentials)
@@ -222,7 +224,7 @@ during an upgrade. When the API server has a floating IP, this role is fulfilled
 floating IP even if there is no load balancer. When the API server does not have a floating
 IP, the load balancer virtual IP on the cluster network is used.
 
-## Restrict Access to the API server
+### Restrict Access to the API server
 
 > **NOTE**
 >

docs/book/src/development/ci.md

@@ -5,6 +5,7 @@
 - [Hacking CI for the E2E tests](#hacking-ci-for-the-e2e-tests)
   - [Prow](#prow)
   - [DevStack](#devstack)
+    - [DevStack OS](#devstack-os)
     - [Configuration](#configuration)
     - [Build order](#build-order)
     - [Networking](#networking)
@@ -25,7 +26,7 @@ The E2E tests require an OpenStack cloud to run against, which we provision duri
 
 The entry point for the creation of the test DevStack is `hack/ci/create_devstack.sh`, which is executed by `scripts/ci-e2e.sh`. We create 2 instances: `controller` and `worker`. Each will provision itself via cloud-init using config defined in `hack/ci/cloud-init`.
 
-## DevStack OS
+### DevStack OS
 
 In GCE, DevStack is installed on a community-maintained Ubuntu 20.04 LTS cloud image. The cloud-init config is also intended to work on CentOS 8, and this is known to work as of 2021-01-12. However, note that this is not regularly tested. See the comment in `hack/ci/gce-project.sh` for how to deploy on CentOS.
 

docs/book/src/development/development.md

@@ -10,7 +10,10 @@
   - [Running E2E tests locally](#running-e2e-tests-locally)
     - [Support for clouds using SSL](#support-for-clouds-using-ssl)
     - [Support for clouds with multiple external networks](#support-for-clouds-with-multiple-external-networks)
-    - [OpenStack prerequisites](#openstack-prerequisites)
+    - [E2E test environment](#e2e-test-environment)
+      - [Requirements](#requirements)
+      - [Create E2E test environment](#create-e2e-test-environment)
+        - [OpenStack](#openstack)
   - [Running E2E tests using rootless podman](#running-e2e-tests-using-rootless-podman)
     - [Host configuration](#host-configuration)
     - [Running podman system service to emulate docker daemon](#running-podman-system-service-to-emulate-docker-daemon)

docs/book/src/topics/external-cloud-provider.md

@@ -3,7 +3,7 @@
 **Table of Contents**  *generated with [DocToc](https://github.com/thlorenz/doctoc)*
 
 - [External Cloud Provider](#external-cloud-provider)
-  - [Steps](#steps)
+  - [Steps of using external cloud provider template](#steps-of-using-external-cloud-provider-template)
 
 <!-- END doctoc generated TOC please keep comment here to allow auto update -->