You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Replace `<IONOS_API_TOKEN>` with your actual IONOS API token.
43
43
44
-
### Step 2: Configure ExternalDNS
44
+
### Step 2: Configure ExternalDNS
45
45
46
46
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` .
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:
93
93
94
94
```yaml
95
95
apiVersion: apps/v1
@@ -128,8 +128,6 @@ In this step, we will create a `Service` manifest to expose the `echoserver` app
128
128
129
129
Save the following content in a file named `echoserver-service.yaml`:
130
130
131
-
132
-
133
131
```yaml
134
132
apiVersion: v1
135
133
kind: Service
@@ -144,8 +142,8 @@ spec:
144
142
selector:
145
143
app: echoserver
146
144
```
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`.
148
145
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`.
149
147
150
148
Next, apply the service:
151
149
@@ -203,6 +201,7 @@ Use the following `curl` command to verify that the application is accessible:
203
201
```bash
204
202
curl -I http://app.example.com
205
203
```
204
+
206
205
Replace app.example.com with the subdomain you configured in your DNS zone.
207
206
208
207
**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
215
214
HTTP/1.1 200 OK
216
215
```
217
216
218
-
> **Troubleshooting:**
217
+
> **Troubleshooting:**
219
218
>
220
219
>If you encounter any issues, verify the following:
221
-
>
220
+
>
222
221
> - The DNS record for `app.example.com` (replace with your own subdomain configured in IONOS Cloud DNS) has been created in IONOS Cloud DNS.
223
222
> - The ingress controller is running and properly configured in your Kubernetes cluster.
224
223
> - The `echoserver` application is running and accessible within the cluster.
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