Let’s Encrypt, OAuth 2, and Kubernetes Ingress
Suggestion to anybody reading this: don't use a DaemonSet for this. This really ought to be a Deployment of nginx-ingress resources behind a service exposed as `type: LoadBalancer` (if you're in a cloud-provider that supports LoadBalancer services). Then just create DNS aliases and configure nginx to do session affinity if needed, etc. Not only will it be able to scale with your load instead of cluster size, but you can actually update it in a rolling update already; DaemonSets cannot yet do that.<p>Really the most important part, though, is that DaemonSets are for services that <i>need</i> to run on each host. Like a log collection service [1] or prometheus node exporter [2].<p>[1] <a href="https://github.com/kubernetes/kubernetes/tree/master/cluster/addons/fluentd-elasticsearch" rel="nofollow">https://github.com/kubernetes/kubernetes/tree/master/cluster...</a><p>[2] <a href="https://github.com/prometheus/node_exporter" rel="nofollow">https://github.com/prometheus/node_exporter</a>