...
CircleCI: There's one line of setup that goes into the project – into kube config. but aside from that we're only using a config.yml file. defined how to build and push, and defined how to deploy. Will need to be re-written when we go live (pushes to press-test and drupal8 branch). There are fancier ways to go about the file (multiple branches depending on which branch updates and so on) Recommendations: stick with circle, maybe add a line to catch when a build fails and alert us. Add behat tests in circle to catch when a build fails. In the future we may want the ability to push specific branches to staging, but not a current requirement. (maybe master never deploys to production?)
Kubernettes: Overall seems to be super successful with our setup. Ryan has been very good at identifying what we containers need to be on k8s and so on. Recommendations: Ryan may want to move NGINX out of docker and into k8s (future enhancement). May need to set up more alerts for K8s for Ryan. This is part of the evolving conversation for circle vs k8s and server team vs devs (don't debundle drupal and php)
Composer file: updating composer itself is set at the docker level, but otherwise composer is working smoothly.
...