Just figured I would add this for posterity sake. The Pearson Bitesize team open sourced our deployment pipeline plugin at KubeCon Seattle on Monday Nov. 8th 2016. Kubernetes Continuous Deployment Pipeline https://github.com/pearsontechnology/deployment-pipeline-jenkins-plugin
We recently upgraded Kube-dns.
Having used SkyDNS up to this point, we ran into some unexpected performance issues. In particular we were seeing pretty exaggerated response times from kube-dns when making requests it is not authoritative on (i.e. not cluster.local). Fortunately this was on a cluster not yet serving any production customers. It took several hours…
Kubernetes Init containers. Alright, I’m just going to tell the truth here. When I first started reading about them, I didn’t get it. I thought to myself, “with all the other stuff they could be doing right now at this early stage of Kubernetes, what the hell were they thinking? Seriously?” But that’s because I…
I’m just gonna leave this here. From our team to yours. https://github.com/pearsontechnology/bitesize-authz-webhook All props go to Simas
Reading through the release notes of Kubernetes 1.4, I came across some fantastical news. News so good, I should have expected it. News that could not come at a better time. I’m talking about container guarantees, or what Kubernetes calls Resource Quality of Service. Let me be frank here, its like the Kubernetes team was…
Recently we had the desire to cluster Consul (Hashicorps K/V store) without calling out to Atlas. We deploy many clusters per day as we are constantly testing and we want Consul to simply bring itself up without having to reach out over the internet. So we added a few changes to our Consul setup, so here…
First off, mad props go out to Ben Somogyi and Martin Devlin. They have been digging deep on this and have made great progress. I wanted to make sure I call them out and all the honors go to them. I just have the honor of telling you about it. You might be thinking right…
So I figured we would have a little fun with this post. It doesn’t all have to be highly technical right? As with any new platform, application or service the opportunity for learning what NOT to do is ever present and when taken in the right light, can be quite hilarious for others to consume….
Everything thing mentioned has been POCed and proven to work so far in testing. We run an application called Pulse in which we demoed it staying up throughout this A/B migration process. Recently the team went through an exercise on how to deploy/manage a complete cluster upgrade. There were a couple options discussed along with…
Recently we chose to migrate our container registry to GCloud for the following reasons: We didn’t want to host it ourselves anymore. We wanted to distribute our docker images world wide for consumption in our Multi-Region scenario. We run Google Apps/Email and we could just hook into that for permissions to the registry. Its as…
Tagsaffinity anti-affinity aws build pipeline CI/CD pipeline codegen conference consul container containers continuous deployment cron devops docker envconsul fluentd hashicorp hipchat hubot IFTTT ingress ingress controller jenkins job jobs kafka kube-dns kubecon kubernetes kubernetes api kubernetes scheduler migration multiaz mysql nginx python python-client rds registry serviceaccount st2 stackstorm talk terraform vault