Rails on Kubernetes - part 5: K8s Yaml Files This is one of a series of blog posts in which I’m walking through the process of deploying a rails application to a kubernetes cluster. Part one is here, and the previous article is here. We’ve got our simple rails application running via docker-compose. Now we’re going to set up the configuration files we need to deploy it to our kubernetes cluster.

This is one of a series of blog posts in which I’m walking through the process of deploying a rails application to a kubernetes cluster. Part one is here, and the previous article is here. To test our containerised Rails app locally, before we try to deploy it to our kubernetes cluster, we can use docker-compose. First of all, stop the postgresql container, otherwise things might get confusing:

This is one of a series of blog posts in which I’m walking through the process of deploying a rails application to a kubernetes cluster. Part one is here, and the previous article is here. Kubernetes runs containers, so before we can deploy our application to kubernetes, we need to containerise it. In this section, we’re going to take our rails application and package it up as a Docker image.

This is one of a series of blog posts in which I’m walking through the process of deploying a rails application to a kubernetes cluster. Part one is here, and the previous article is here Our rails application can connect to our database. So now let’s get it to do what we want, which is to store and display a value, and increment it whenever we click a button.

This is the second part of a series of posts on how to deploy a ruby on rails application to a kubernetes cluster. If you want to start from the beginning, part one is here Now that we have our kubernetes cluster, we need to create something to deploy onto it. For this walkthrough, I’m going to create a trivial rails application, which just stores a counter in a database, and allows you to increment it by clicking a button.