Skip to content

Commit 42f167c

Browse files
committed
docs: prefix ovhcloud guide section headings with 'step'
Update the numbered section headings in the Talos v1.13 OVHcloud installation guide to include the word 'Step' before each number. This improves readability and makes it clearer to users that these headings represent sequential steps in the installation procedure. Signed-off-by: Kevin Tijssen <kevin.tijssen@siderolabs.com>
1 parent 2766125 commit 42f167c

1 file changed

Lines changed: 7 additions & 7 deletions

File tree

  • public/talos/v1.13/platform-specific-installations/cloud-platforms

public/talos/v1.13/platform-specific-installations/cloud-platforms/ovhcloud.mdx

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ export LOADBALANCER_NAME=loadbalancer-001
3434
export LOADBALANCER_FLAVOR_NAME=small
3535
```
3636

37-
## 1. Create the image
37+
## Step 1. Create the image
3838

3939
First, download the <a href={`https://factory.talos.dev/image/376567988ad370138ad8b2698212367b8edcb69b5fd68c80be1f2ec7d603b4ba/${release_v1_13}/akamai-amd64.raw.gz`}> OpenStack image</a> from [Image Factory](https://factory.talos.dev/).
4040
These images are called `openstack-$ARCH.raw.xz`.
@@ -53,7 +53,7 @@ openstack image create $IMAGE_NAME \
5353
--progress
5454
```
5555

56-
## 2. Network infrastructure (Optional)
56+
## Step 2. Network infrastructure (Optional)
5757

5858
If you have an existing network infrastructure, you can skip this step.
5959
If not, you can follow the instructions below to create the necessary network infrastructure for your cluster.
@@ -98,7 +98,7 @@ Ports have been opened to ensure that connectivity from both inside and outside
9898
You will want to allow, at a minimum, ports 6443 (Kubernetes API server) and 50000 (Talos API) from external sources.
9999
It is also recommended to allow communication over all ports from within the subnet.
100100

101-
## 3. Compute
101+
## Step 3. Compute
102102

103103
Once the image is uploaded and the network infrastructure is in place, we can create our compute instances.
104104
We will create 3 control plane nodes.
@@ -144,7 +144,7 @@ for i in $( seq 1 3 ); do
144144
done
145145
```
146146

147-
## 4. Cluster configuration
147+
## Step 4. Cluster configuration
148148

149149
Now that we have our compute instances and load balancer set up, we can generate our cluster configuration files with `talosctl`.
150150
We need to get the Public IP of the Load Balancer as this is our Kubernetes API endpoint, and the Public IPs of the control plane nodes as addional-sans for the API certificate.
@@ -165,7 +165,7 @@ talosctl gen config talos-ovhcloud https://$LOADBALANCER_VIP:6443 \
165165
--additional-sans $CP1_IP,$CP2_IP,$CP3_IP
166166
```
167167

168-
## 5. Applying configuration and bootstrapping the cluster
168+
## Step 5. Applying configuration and bootstrapping the cluster
169169

170170
With our configuration file generated, we can now apply it to our control plane nodes and bootstrap the cluster.
171171

@@ -199,15 +199,15 @@ talosctl config node $CP1_IP
199199

200200
You should now be able to interact with your cluster with `talosctl`.
201201

202-
## 6. Retrieve the `kubeconfig`
202+
## Step 6. Retrieve the `kubeconfig`
203203

204204
At this point we can retrieve the admin `kubeconfig` by running:
205205

206206
```bash
207207
talosctl kubeconfig .
208208
```
209209

210-
## 7. Add worker nodes to the cluster
210+
## Step 7. Add worker nodes to the cluster
211211

212212
```bash
213213
# Create worker node with the user data file

0 commit comments

Comments
 (0)