Using GitHub and Travis, we have now automated the entire workflow from changing the application's source code over building new binaries to creating new Docker images and pushing them to a container registry. That is great, but we are still missing one crucial step, that is, getting the new container images to run in your production environment.
In the previous chapters, you have already worked with Kubernetes and deployed your containerized applications into a Minikube environment. For this section, we will assume that you already have a publicly accessible Kubernetes environment up and running (for example, using a kops-provisioned cluster in AWS or the Azure Container Service).
First of all, Travis CI will need to access your Kubernetes cluster. For this, you can create a service account in your Kubernetes cluster. This Service Account will then...
