Disclaimer: while CSI is a vendor-agnostic interface, this article will mainly focus on AWS and GCP implementations specifically, since these are the platforms on which we’ve had to conduct migration to CSI. Introduction For volume management, Kubernetes originally shipped with in-tree drivers for various cloud providers, interfacing with the underlying platform on which the cluster […]

Container technology is causing a structural change in the entire cloud-computing world. A change we embrace at Kumina. In this first post from our blog post series ‘Containerisation with Kubernetes and Docker’, we’ll provide you with a simple introduction to the concept ‘containerisation’ and about how containers relate to virtual machines (VM).

At Kumina, we’re strong users of the Amazon AWS cloud computing platform. We’ve been using EC2 instances for quite some time and are currently working on expanding this by making use of Kubernetes. To further optimise our solutions, we’ve developed a new utility called awssyncer, which is as of now available on GitHub! awssyncer is a utility written in C++ that uses Linux’s inotify to keep track of local modifications to a directory on disk. The purpose of this utility is to use these inotify events to determine which files need to be synced back into S3. This utility thus provides continuous one-way sychronisation from local disk to S3. A simple container startup script is used to sync files from S3 to local disk on startup. Though we realise that this utility is fairly specific to our situation at hand, we do invite all of you to give it a try.

Yesterday evening we returned from LOADays 2013 in Antwerp, This blogpost describes some things we learned and want to implement in the (near) future.