router ssl first pass

rough draft mind dump for ssl
Certs are a great candidate for referenced secrets, but we're not there yet unfortunately.  Until, let's do the naive assumption that the cert channel is secure and that you store them on disk by recreating from the route info as necessary.  Or were you asking for more?

> On Dec 19, 2014, at 1:40 PM, Paul <notifications@github.com> wrote:
> 
> In docs/routing.md:
> 
> > +            Certificate tls.Certificate                                                                             
> > +      }
> > +      
> > +      type SSLTerminationType string
> > +      
> > +      const (
> > +          Edge      SSLTerminationType = "edge"
> > +          Pod       SSLTerminationType = "pod"
> > +          Reencrypt SSLTerminationType = "reencrypt"
> > +      )
> > +    
> > +Update the route definition to call `tls.Certificate.LoadX509KeyPair` and save the value in `Route.Certificate`
> > +      
> > +#####Router Changes
> > +      
> > +1. Where will the certificate files be stored when the route is created, is this dependent on the persistent disk upstream issue?
> your assumptions on my adoption preparedness are correct   
> 
> My question was more for the router side of things. When creating the route we'll store the cert in etcd. When the router creates the route it will need to point to a file on disk. I think the easiest thing for me to do is to assume I will pass a storage parameter to the pod or use a default directory and that directory can be a mounted PD or a local directory. Acceptable?
> 
> —
> Reply to this email directly or view it on GitHub.
>