Skip to content

Commit d0874a3

Browse files
docs(tutorials): improve formatting and clarity in IONOS Cloud tutorial
1 parent 12e6681 commit d0874a3

File tree

1 file changed

+9
-8
lines changed

1 file changed

+9
-8
lines changed

docs/tutorials/ionoscloud.md

Lines changed: 9 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ kubectl create secret generic ionos-credentials --from-literal=api-key='<IONOS_A
4141

4242
Replace `<IONOS_API_TOKEN>` with your actual IONOS API token.
4343

44-
### Step 2: Configure ExternalDNS
44+
### Step 2: Configure ExternalDNS
4545

4646
Create a Helm values file for the ExternalDNS Helm chart that includes the webhook configuration. In this example, the values file is called `external-dns-ionos-values.yaml` .
4747

@@ -89,7 +89,7 @@ helm upgrade --install external-dns external-dns/external-dns -f external-dns-io
8989

9090
### Step 1: Create a Deployment
9191

92-
In this step we will create `echoserver` application manifest with the following content:
92+
In this step we will create `echoserver` application manifest with the following content:
9393

9494
```yaml
9595
apiVersion: apps/v1
@@ -128,8 +128,6 @@ In this step, we will create a `Service` manifest to expose the `echoserver` app
128128

129129
Save the following content in a file named `echoserver-service.yaml`:
130130

131-
132-
133131
```yaml
134132
apiVersion: v1
135133
kind: Service
@@ -144,8 +142,8 @@ spec:
144142
selector:
145143
app: echoserver
146144
```
147-
**Note:** Replace `app.example.com` with a subdomain of your DNS zone configured in IONOS Cloud DNS. For example, if your DNS zone is `example.com`, you can use a subdomain like `app.example.com`.
148145

146+
**Note:** Replace `app.example.com` with a subdomain of your DNS zone configured in IONOS Cloud DNS. For example, if your DNS zone is `example.com`, you can use a subdomain like `app.example.com`.
149147

150148
Next, apply the service:
151149

@@ -203,6 +201,7 @@ Use the following `curl` command to verify that the application is accessible:
203201
```bash
204202
curl -I http://app.example.com
205203
```
204+
206205
Replace app.example.com with the subdomain you configured in your DNS zone.
207206

208207
**Note:** Ensure that your DNS changes have propagated and that the hostname resolves to the correct IP address before running the command.
@@ -215,10 +214,10 @@ You should see an HTTP response header indicating that the application is runnin
215214
HTTP/1.1 200 OK
216215
```
217216

218-
> **Troubleshooting:**
217+
> **Troubleshooting:**
219218
>
220219
>If you encounter any issues, verify the following:
221-
>
220+
>
222221
> - The DNS record for `app.example.com` (replace with your own subdomain configured in IONOS Cloud DNS) has been created in IONOS Cloud DNS.
223222
> - The ingress controller is running and properly configured in your Kubernetes cluster.
224223
> - The `echoserver` application is running and accessible within the cluster.
@@ -252,4 +251,6 @@ kubectl delete -f echoserver-ingress.yaml
252251

253252
## Summary
254253

255-
In this tutorial, you successfully deployed ExternalDNS webhook with IONOS Cloud DNS as the provider. You created a Kubernetes deployment, service, and ingress, and verified that DNS records were created and the application was accessible. You also learned how to clean up the resources when they are no longer needed.
254+
In this tutorial, you successfully deployed ExternalDNS webhook with IONOS Cloud DNS as the provider.
255+
You created a Kubernetes deployment, service, and ingress, and verified that DNS records were created and the application was accessible.
256+
You also learned how to clean up the resources when they are no longer needed.

0 commit comments

Comments
 (0)