Arne arnesacnussem

Nginx TLS SNI routing, based on subdomain pattern

Nginx can be configured to route to a backend, based on the server's domain name, which is included in the SSL/TLS handshake (Server Name Indication, SNI).
This works for http upstream servers, but also for other protocols, that can be secured with TLS.

prerequisites

at least nginx 1.15.9 to use variables in ssl_certificate and ssl_certificate_key.
check nginx -V for the following:
```
...
TLS SNI support enabled
```

Reddit post (Archived)

Table of Content

What to expect?
- Some TLDR about the idea behind
Prerequisites
- Hardware
- System & Software
Update: Attention for MUXless laptop

	#!/bin/bash
	#
	# Written by Chris Arceneaux
	# GitHub: https://github.com/carceneaux
	# Email: carcenea@gmail.com
	# Website: http://arsano.ninja
	#
	# Note: This code is a stop-gap to erase Job Artifacts for a project. I HIGHLY recommend you leverage
	# "artifacts:expire_in" in your .gitlab-ci.yml
	#

	# This will use osd.5 as an example
	# ceph commands are expected to be run in the rook-toolbox
	1) disk fails
	2) remove disk from node
	3) mark out osd. `ceph osd out osd.5`
	4) remove from crush map. `ceph osd crush remove osd.5`
	5) delete caps. `ceph auth del osd.5`
	6) remove osd. `ceph osd rm osd.5`
	7) delete the deployment `kubectl delete deployment -n rook-ceph rook-ceph-osd-id-5`
	8) delete osd data dir on node `rm -rf /var/lib/rook/osd5`