feat: configure dedicated server proxy
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This commit is contained in:
parent
e787359c54
commit
a86a0cb539
8 changed files with 91 additions and 91 deletions
55
deploy/nginx/README.md
Normal file
55
deploy/nginx/README.md
Normal file
|
|
@ -0,0 +1,55 @@
|
|||
# Dedicated-server reverse proxy
|
||||
|
||||
Production exposes only the Go Guess application through Kubernetes NodePort
|
||||
`31374`. PostgreSQL and RabbitMQ remain available only through their
|
||||
cluster-internal services.
|
||||
|
||||
## DNS
|
||||
|
||||
In one.com, create an `A` record for `goguess.urpi.be` pointing to the dedicated
|
||||
server's public IPv4 address. Add an `AAAA` record only when the server and its
|
||||
firewall are configured for public IPv6. Wait for:
|
||||
|
||||
```bash
|
||||
dig +short goguess.urpi.be
|
||||
```
|
||||
|
||||
to return the dedicated server address before requesting a certificate.
|
||||
|
||||
## Nginx and Certbot
|
||||
|
||||
The included virtual host assumes Nginx runs on the Kubernetes node and can
|
||||
reach the NodePort at `127.0.0.1:31374`.
|
||||
|
||||
```bash
|
||||
sudo install -m 0644 deploy/nginx/goguess.urpi.be.conf \
|
||||
/etc/nginx/sites-available/goguess.urpi.be.conf
|
||||
sudo ln -s /etc/nginx/sites-available/goguess.urpi.be.conf \
|
||||
/etc/nginx/sites-enabled/goguess.urpi.be.conf
|
||||
sudo nginx -t
|
||||
sudo systemctl reload nginx
|
||||
sudo certbot --nginx -d goguess.urpi.be
|
||||
sudo certbot renew --dry-run
|
||||
```
|
||||
|
||||
Certbot adds the HTTPS listener, certificate paths, and HTTP-to-HTTPS redirect
|
||||
to this virtual host. Allow inbound TCP ports `80` and `443`. Do not expose
|
||||
NodePort `31374`, PostgreSQL `5432`, RabbitMQ `5672`, or RabbitMQ management
|
||||
ports to the public internet. If Nginx is not on a Kubernetes node, replace
|
||||
`127.0.0.1` in `proxy_pass` with a private cluster-node address and allow
|
||||
`31374` only from the Nginx server.
|
||||
|
||||
## Deploy and verify
|
||||
|
||||
Deploy the production profile:
|
||||
|
||||
```bash
|
||||
make helm-deploy-production
|
||||
kubectl -n go-guess-production get pods
|
||||
kubectl -n go-guess-production get service go-guess
|
||||
curl --fail http://127.0.0.1:31374/api/health
|
||||
curl --fail https://goguess.urpi.be/api/health
|
||||
```
|
||||
|
||||
The `go-guess` service should show `80:31374/TCP`. The PostgreSQL and RabbitMQ
|
||||
services should remain `ClusterIP` services without NodePorts.
|
||||
Loading…
Add table
Add a link
Reference in a new issue