Over the last few months hundreds of users have used Deliverybot to deploy code to a variety of platforms. From Kubernetes, Firebase to Heroku. I’ve seen the value of Deliverybot go up as GitHub actions becomes a tool that more and more organizations are jumping into to test their code.
Deploy your code on GitHub right from Slack. Involves your team in the conversation and keeps a living breathing view of documentation. Deliverybot has a slack integration that takes just a few seconds to install!
A year or so ago I came across this interesting feature in GitHub called the deployments api. It seemed like a bit of a lost section in the GitHub docs, disconnected from other component and unlike pretty much everything else in GitHub I really hadn’t used this. I’ve spent some time investigating the deployments API over the last month or so and wanted to explain this for those of you who have hit this and wondered, what is this thing?
Canary deployments are a very effective way of testing new code on a subset of a user base. They significantly reduces the blast radius of a deployment that may be tricky to roll out by only exposing it to a subset of traffic. This post will dive into how to achieve this within Kubernetes but also in a deployment automation friendly way
This post discusses one of the most common deployment tools for Kubernetes. Helm is the “package manager for Kubernetes” and therefore has become one of the most common tools for managing application deployments.
Kustomize is a new way of templating in Kubernetes. It's not strictly a templating system — a better way to describe it is “customization for your Kubernetes yaml files” — but achieves the same goal for most of us. This post explores this new system.