https://github.com/con2/redirects
Redirects en masse using ingress-nginx
https://github.com/con2/redirects
Last synced: 5 months ago
JSON representation
Redirects en masse using ingress-nginx
- Host: GitHub
- URL: https://github.com/con2/redirects
- Owner: con2
- Created: 2020-11-25T20:29:16.000Z (over 5 years ago)
- Default Branch: main
- Last Pushed: 2025-08-20T17:07:14.000Z (10 months ago)
- Last Synced: 2025-08-20T19:27:20.184Z (10 months ago)
- Size: 30.3 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Redirects en masse on Kubernetes
We have a whole host of hostnames we want to redirect to another hostname. This is the Way.
## Why not just use the `nginx.ingress.kubernetes.io/temporal-redirect` annotation?
It takes place **before** [cert-manager](https://cert-manager.io/) challenge solvers, effectively breaking LetsEncrypt for domains using it. There are [some](https://github.com/jetstack/cert-manager/issues/235) [issues](https://github.com/jetstack/cert-manager/issues/235) that have been filed against `cert-manager` and `ingress-nginx` solving the similar case for HTTP -> HTTPS redirect and basic auth, but not `temporal-redirect` specifically.
So instead we opt for an `nginx` pod with configuration mounted from a ConfigMap into under `/etc/nginx/conf.d`.
## Configuration
Use `kubernetes/default.vars.yaml` as reference and `kubernetes/production.vars.yaml` as example.
## Building and deploying
emsk -E production -- run -n redirects