Deployment Manager

Deployment Manager (DM) provides parameterized templates for Kubernetes clusters.

You can use it deploy ready-to-use types, such as:

• Replicated Service
• Redis

As you can see, types live in ordinary Github repositories. This repository is a DM type registry.

You can also use DM to deploy simple templates that use existing types, such as:

• Guestbook
• Deployment Manager

As you can see, a template is just a YAML file that supplies parameters to instantiate types. (Yes, you're reading that second example correctly. It uses DM to deploy itself. See examples/bootstrap/README.md for more information)

DM runs server side, on your Kubernetes cluster, so it can tell you what types you've instantiated in the cluster, and even what resources comprise a given instance. So, you can ask questions like:

• Show me all the Redis slaves running in this cluster.
• Show me all the resources used by Redis.

Because DM stores its state in the cluster, not on your workstation, you can ask those questions from any client at any time.

Please hang out with us in the Slack chat room and/or the Google Group for the Kubernetes configuration SIG. Your feedback and contributions are welcome.

Installing Deployment Manager

Follow these 3 steps to install DM:

1. Make sure your Kubernetes cluster is up and running, and that you can run kubectl commands against it.
2. Clone this repository into the src folder of your GOPATH, if you haven't already.
3. Use kubectl to intall DM into your cluster:

kubectl create -f install.yaml

That's it. You can now use kubectl to see DM running in your cluster:

kubectl get pod,rc,service

If you see expandybird-service, manager-service, resourcifier-service, and expandybird-rc, manager-rc and resourcifier-rc with pods that are READY, then DM is up and running!

The easiest way to interact with Deployment Manager is through kubectl proxy:

kubectl proxy --port=8001 &

This command starts a proxy that lets you interact with the Kubernetes api server through port 8001 on localhost. dm uses http://localhost:8001/api/v1/proxy/namespaces/default/services/manager-service:manager as the default service address for DM.

Using Deployment Manager

You can use dm to deploy a type from the command line. This command deploys a redis cluster with two workers from the type definition in this repository:

dm deploy redis/v1

When you deploy a type, you can optionally supply values for input parameters, like this:

dm --properties workers=3 deploy redis/v1

When you deploy a type, dm generates a template from the type and input paramaters, and then deploys it.

You can also deploy an existing template, or read one from stdin. This command deploys the canonical Guestbook example from the examples directory:

dm deploy examples/guestbook/guestbook.yaml

You can now use kubectl to see Guestbook running:

kubectl get service

Look for frontend-service. If your cluster supports external load balancing, it will have an external IP assigned to it, and you can navigate to it in your browser to see the guestbook in action.

For more information about this example, see examples/guestbook/README.md

Additional commands

The command line tool makes it easy to configure a cluster from a set of predefined types.

Uninstalling Deployment Manager

You can uninstall Deployment Manager using the same configuration file:

kubectl delete -f install.yaml

Creating a type registry

All you need to create a type registry is a Github repository with top level file named registry.yaml, and a top level folder named types that contains type definitions.

A type definition is just a folder that contains one or more versions, like /v1, /v2, etc.

A version is just a folder that contains a type definition. As you can see from the examples above, a type definition is just a Python or Jinja file plus an optional schema.

Building the container images

This project runs Deployment Manager on Kubernetes as three replicated services. By default, install.yaml uses prebuilt images stored in Google Container Registry to install them. However, you can build your own container images and push them to your own project in the Google Container Registry:

1. Set the environment variable PROJECT to the name of a project known to gcloud.
2. Run the following command:

make push

Design of Deployment Manager

There is a more detailed design document available.

Status of the project

The project is still under active development, so you might run into issues. If you do, please don't be shy about letting us know, or better yet, contributing a fix or feature. We use the same development process as the main Kubernetes repository.

Relationship to Google Cloud Platform

DM uses the same concepts and languages as Google Cloud Deployment Manager, but creates resources in Kubernetes clusters, not in Google Cloud Platform projects.