http://code.secondbit.org/ducky/nginx/ en-us ducky/nginx Changelog http://code.secondbit.org/ducky/nginx/rev/16bf0d2d11d1 http://code.secondbit.org/ducky/nginx/rev/16bf0d2d11d1 changeset 16bf0d2d11d1 branch default bookmark tag tip user Paddy <paddy@secondbit.org> description Make nginx kubernetes-ready.

Add our upstream definitions, to route requests to our ducky-authd service and
our ducky-subscriptionsd service.

Remove the test handler that was installed at /.

Update our proxy-redirect rules so the proxy redirects actually work now, and
what used to redirect us to /profiles now redirects us to /auth/profiles.

Define a Replication Controller that will spin up nginx pods for us and
auto-attach the necessary JWT secret volume to read our JWT secret.

Define a Service that will route to nginx for us. files nginx/conf/nginx.conf
replication-controllers/nginx.json
services/nginx.json
]]> Paddy <paddy@secondbit.org> Tue, 30 Jun 2015 00:40:12 -0400 http://code.secondbit.org/ducky/nginx/rev/20206854e82f http://code.secondbit.org/ducky/nginx/rev/20206854e82f changeset 20206854e82f branch bookmark tag user Paddy <paddy@secondbit.org> description The beginning of an nginx reverse proxy.

Set up a reverse proxy that is based on secondbit/nginx and uses the lua
authenticaiton. Right now, this passes correctly to an auth service and a
subscriptions service. It also had a debug endpoint for echoing back the
headers the request was made with.

Right now, everything is super-fragilely hard-coded to use the IP of Paddy's
local machine, which obviously should not be the case. Still need to figure out
how we're going to do this to work with kubernetes _and_ locally. Kubernetes
will give us `my-svc.my-namespace.svc.cluster.local` DNS names to route,
round-robin style, to the correct backend, but that's hard to emulate locally (I
assume? I haven't looked into it). files Dockerfile
nginx/conf/nginx.conf
]]> Paddy <paddy@secondbit.org> Mon, 22 Jun 2015 00:48:17 -0400