Deploying Kubernetes on a private cloud environment like VMware vSphere or OpenStack is great for developer innovation speed, security, and to ensure compliance. But be careful. Changing credentials (password) of the user that deployed the cluster may have unexpected consequences!
GKE, Google Container Engine, is an easy way of getting started with a managed Kubernetes service. In this post, we show how to get started from scratch and wind up with a cluster that is provisioned using Terraform. Defining your infrastructure in Terraform means that you can easily create a replica of your GKE environment. This is useful for e.g. a staging environment or to recover from a disaster. Let’s get started!
This article will explore building geo-distributed applications, with a particular focus on using NewSQL databases.
If you can endure some theory, you will be richly awarded in the end with sample code to run your WordPress-powered blog or CMS across three (!) Kubernetes clusters in three (!) different geographical regions.
Backups are important. How many times have you read that you should always backup before doing this or that? How many times did the documentation actually explain how and what you should backup? And if it did, did it also explain how to restore the backup if needed? Unfortunately, backup and restore documentation is often lacking. And this is the case even for serious projects like Kubernetes. Read on to learn more about backups in Kubernetes how to do them, what to include and why.