dghubble/tarpoon
1
0
Fork 0
forked from barak/tarpoon
Code Releases Activity
tarpoon/vendor/k8s.io/kubernetes/cluster/addons/addon-manager
History
Dalton Hubble 5b3d5e81bd Add glide.yaml and vendor deps
2016-12-03 22:43:32 -08:00
..
CHANGELOG.md Add glide.yaml and vendor deps 2016-12-03 22:43:32 -08:00
Dockerfile Add glide.yaml and vendor deps 2016-12-03 22:43:32 -08:00
kube-addons.sh Add glide.yaml and vendor deps 2016-12-03 22:43:32 -08:00
Makefile Add glide.yaml and vendor deps 2016-12-03 22:43:32 -08:00
namespace.yaml Add glide.yaml and vendor deps 2016-12-03 22:43:32 -08:00
README.md Add glide.yaml and vendor deps 2016-12-03 22:43:32 -08:00

README.md

addon-manager

The addon-manager periodically kubectl applys the Kubernetes manifest in the /etc/kubernetes/addons directory, and handles any added / updated / deleted addon.

It supports all types of resource.

The addon-manager is built for multiple architectures.

How to release

  1. Change something in the source
  2. Bump VERSION in the Makefile
  3. Bump KUBECTL_VERSION in the Makefile if required
  4. Build the amd64 image and test it on a cluster
  5. Push all images
# Build for linux/amd64 (default)
$ make push ARCH=amd64
# ---> gcr.io/google-containers/kube-addon-manager-amd64:VERSION
# ---> gcr.io/google-containers/kube-addon-manager:VERSION (image with backwards-compatible naming)

$ make push ARCH=arm
# ---> gcr.io/google-containers/kube-addon-manager-arm:VERSION

$ make push ARCH=arm64
# ---> gcr.io/google-containers/kube-addon-manager-arm64:VERSION

$ make push ARCH=ppc64le
# ---> gcr.io/google-containers/kube-addon-manager-ppc64le:VERSION

If you don't want to push the images, run make or make build instead

Analytics