This article assumes that user already has a Kubernetes cluster created with GKE-engine up and running. If that is not the case, the user can read Kubernetes cluster on Google Container Engine article which explains how to do so or read the official document.
Let’s Migrate Local Container to Google Container Engine.
Considering that the user already has WordPress application with Mysql 5.7 running on local Docker deployment.
List containers running in the local Docker deployment
A user can list running Docker containers using the ‘docker ps’ command.
Fig. (1) Docker list containers
Set up persistent disk into Google cloud
Create two persistent disks. The user will need to create the disks in the same GCE zone as the Kubernetes cluster. Replace <zone> below with the appropriate zone. The names wordpress-1 and wordpress-2 must match the pdName fields we have specified in gce-volumes.yaml
After performing above steps, user has to login to DNS service provider and change ‘A’ record(s) for pointing it to new created load balancer’s IP which was created while WordPress deployment.
To manage running Docker containers, Google Container Engine is a very powerful cluster manager. It’s built on the open-source Kubernetes system, giving the flexibility to take an advantage of on-premises, hybrid or public cloud infrastructure.