slawek/ok-server
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: update README and Ingress configuration for ok-server to clarify DNS usage

Browse Source
This commit is contained in:
slawek
2026-07-26 21:15:25 +02:00
parent 57d76d013c
commit 9c788b721e
1 changed files with 10 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+10 -2
View File
@@ -119,11 +119,19 @@ Expose the app with one of the two options below.
k3s includes the Traefik ingress controller. The ClusterIP Service and Ingress k3s includes the Traefik ingress controller. The ClusterIP Service and Ingress
in [k3s/expose-ingress.yaml](k3s/expose-ingress.yaml) expose the app on port 80 in [k3s/expose-ingress.yaml](k3s/expose-ingress.yaml) expose the app on port 80
of the node's IP address: for the host name `ok-server.example.org`. Change the `host` value in the
Ingress to your own FQDN and point its DNS record at the node's IP address:
```bash ```bash
kubectl apply -f k3s/expose-ingress.yaml kubectl apply -f k3s/expose-ingress.yaml
curl -si "http://<node-ip>/" curl -si "http://ok-server.example.org/"
```
Without a DNS record you can still test the host rule by mapping the name to
the node's IP address on the curl command line:
```bash
curl -si --resolve ok-server.example.org:80:<node-ip> "http://ok-server.example.org/"
``` ```
By default the app sees a cluster-internal address (for example `10.42.0.1`) By default the app sees a cluster-internal address (for example `10.42.0.1`)