Move build system off of Docker Cloud

minderlabs / demo

Minder Demo App

1 stars 0 forks source link

Move build system off of Docker Cloud #33

Open adamberenzweig opened 7 years ago

adamberenzweig commented 7 years ago

Motivation

Get built artifacts out of source control (packed bundles etc)
Build faster (incremental) by maintaining build workspace between builds (jenkins?)
Docker cloud sucks

roadmap

[ ] Build script that runs webpack etc and then creates docker images, then pushes to docker repo (already have for minderlabs/demo, need for /framework)
[ ] Jenkins
[ ] Migrate to better CI/orchestration system. kubernetes?

adamberenzweig commented 7 years ago

Try deploying to kubernetes anywhere (AWS or GC first?). Keep docker hub for now, but get rid of docker cloud and build locally.

adamberenzweig commented 7 years ago

nginx-proxy doesn't seem to work, I think because of the way kubernetes uses docker diferently.i ssh’ed to container, /tmp/docker.sock exists, but can’t read it... and nginx config gets empty upstream section.

I looked at a few other options for load balancing, https termination, and virtualhost-based routing.

The modern kubernetes way appears to be an Ingress resource, but it's a beta feature. There is an nginx implementation though: https://github.com/nginxinc/kubernetes-ingress

I implemented a basic version of that but some things remain TODO:

[ ] Automate Route53 DNS routing to point to the ingress entry point.
[ ] Automate opening up ports in the security groups to the ingress entry point.
[ ] TLS support for https, configure certs via a Secret object

The first two should eventually be handled by an AWS-specific ingress controller, but it hasn't apepared yet. See https://github.com/kubernetes/contrib/issues/346

adamberenzweig commented 7 years ago

Update in https://github.com/minderlabs/framework/pull/44 Not using Ingress, back to plain service with LoadBalancer, using annotation to configure SSL termination. Will manually configure route53 for now.

adamberenzweig commented 7 years ago

Kubernetes looks good, next steps:

[ ] get rid of k, just dev.minderlabs.com
[x] Figure out prod DNS pattern. (ie do we delegate all of minderlabs.com to route53?)
[ ] Jenkins on dev for CI from master, push to qa deployment on dev cluster (www.dev.minderlabs.com)
[ ] remove login buttons from landing pages, if it's too much work to get them working again.

adamberenzweig commented 7 years ago

DNS: We can use a CNAME at the top-level config (google domains) to alias nicer addresses to the ugly kubernetes-cluster names in the route53 hosted zone. i.e.:

www     CNAME www.prod.k.minderlabs.com
app     CNAME app.prod.k.minderlabs.com
www-dev CNAME www.dev.k.minderlabs.com