You are looking at the documentation of a prior release. To read the documentation of the latest release, please visit here.

Development Guide

This document is intended to be the canonical source of truth for things like supported toolchain versions for building Kubed. If you find a requirement that this doc does not capture, please submit an issue on github.

This document is intended to be relative to the branch in which it is found. It is guaranteed that requirements will change over time for the development branch, but release branches of Kubed should not change.

Build Kubed

Some of the Kubed development helper scripts rely on a fairly up-to-date GNU tools environment, so most recent Linux distros should work just fine out-of-the-box.

Setup GO

Kubed is written in Google’s GO programming language. Currently, Kubed is developed and tested on go 1.8.3. If you haven’t set up a GO development environment, please follow these instructions to install GO.

Download Source

$ go get
$ cd $(go env GOPATH)/src/

Install Dev tools

To install various dev tools for Kubed, run the following command:

$ ./hack/

Build Binary

$ ./hack/
$ kubed version

Run Binary

$ kubed run \
  --secure-port=8443 \
  --kubeconfig="$HOME/.kube/config" \
  --authorization-kubeconfig="$HOME/.kube/config" \
  --authentication-kubeconfig="$HOME/.kube/config" \
  --authentication-skip-lookup \

Dependency management

Kubed uses Glide to manage dependencies. Dependencies are already checked in the vendor folder. If you want to update/add dependencies, run:

$ glide slow

Build Docker images

To build and push your custom Docker image, follow the steps below. To release a new version of Kubed, please follow the release guide.

# Build Docker image
$ ./hack/docker/; ./hack/docker/ push

# Add docker tag for your repository
$ docker tag appscode/kubed:<tag> <image>:<tag>

# Push Image
$ docker push <image>:<tag>

Generate CLI Reference Docs

$ ./hack/gendocs/

Testing Kubed

Unit tests

$ ./hack/ test unit

Run e2e tests

Kubed uses Ginkgo to run e2e tests.

$ ./hack/ test e2e

To run e2e tests against remote backends, you need to set cloud provider credentials in ./hack/config/.env. You can see an example file in ./hack/config/.env.example.