Initial Kubernetes deployment


The steps assume the follow steps described on previous pages have been accomplished:

  1. Created the project on Google Cloud Platform and configured the gcloud and kubectl apps.
  2. Created the cluster and persistent storage.
  3. Customized the configuration files, see Configuring LTD Keeper on Kubernetes.

Step 1. deploy configurations

Deploy the configurations with:

kubectl create -f keeper-secrets-prod.yaml
kubectl create -f keeper-config-prod.yaml
kubectl create -f ssl-proxy-secrets-prod.yaml
kubectl create -f cloudsql-secrets-prod.yaml

You can see they have been deployed with:

kubectl get secrets
kubectl get configmaps

Step 2. deploy services

kubectl create -f ssl-proxy-service.yaml
kubectl create -f keeper-service.yaml

Check for the external IP of the ssl-proxy-service with:

kubectl get services

Set the domain’s A record to this IP. This domain was specified as server-name in keeper-secrets.yaml.

Step 3. Deploy the SSL proxy

kubectl create -f ssl-proxy.yaml

Check that the replication controller exists:

kubectl get rc

And that the nginx-ssl-proxy pod exists:

kubectl get pods

Step 4. Deploy the maintenance pod

We use a standalone maintenance pod to initialize the database.

Deploy the pod:

kubectl create -f keeper-mgmt-pod.yaml

Watch for the pod to be created with kubectl get pods. Once it’s ready, log in:

kubectl exec keeper-mgmt -c uwsgi -i -t /bin/bash

From the uwsgi container’s prompt,

./ createdb
./ init

This will:

  1. Create tables in a blank database.
  2. Seed an administrative user account (based on default-user and default-password fields in the keeper-secrets resource).

exit from the keeper-mgmt shell and then take down the maintenance pod:

kubectl delete pod keeper-mgmt

Wait for the pod to terminate by watching kubectl get pods.

Step 5. Deploy LTD Keeper

As an API server, LTD Keeper is run as a deployment, which is Kubernetes short-hand for a replication controller with Pod templates.

To create a new deployment:

kubectl create -f keeper-deployment.yaml

Check that the replication controller is up:

kubectl get rc

Verify that the pod is deployed with:

kubectl get pods

You can know verify that Keeper is serving over HTTPS:


(Substitute your deployment hostname as necessary.)