Paragon1970

kubernetes.click-ops

Generalizing to your own Kubernetes cluster
A note on non-standard kops and nodeup binaries
Installing required binaries
Setting up "permanent" resources
Creating the cluster
Administering the cluster
Other operations on the cluster
Updating your local state

Overview

This gist is based on the information available at golang/dep, only slightly more terse and annotated with a few notes and links primarily for my own personal benefit. It's public in case this information is helpful to anyone else as well.

I initially advocated Glide for my team and then, more recently, vndr. I've also taken the approach of exerting direct control over what goes into vendor/ in my Dockerfiles, and also work from isolated GOPATH environments on my system per project to ensure that dependencies are explicitly found under vendor/.

At the end of the day, vendoring (and committing vendor/) is about being in control of your dependencies and being able to achieve reproducible builds. While you can achieve this manually, things that are nice to have in a vendoring tool include:

	#!/usr/bin/env bash

	set -e

	CONTEXT="$1"

	if [[ -z ${CONTEXT} ]]; then
	echo "Usage: $0 KUBE-CONTEXT"
	exit 1
	fi