k3s/cluster/addons/addon-manager
Ben Breslauer e82c3fbd73 Add user-specified kubectl arguments to addons start script 2016-08-10 18:08:01 -07:00
..
Dockerfile Remove "All rights reserved" from all the headers. 2016-06-29 17:47:36 -07:00
Makefile Fix the way addon-manager handles non-namespaced objects 2016-07-05 10:37:30 +02:00
README.md ConfigMap added to kube addon manager. 2016-07-11 13:54:18 +01:00
kube-addon-update.sh Add user-specified kubectl arguments to addons start script 2016-08-10 18:08:01 -07:00
kube-addons.sh Add user-specified kubectl arguments to addons start script 2016-08-10 18:08:01 -07:00
namespace.yaml run kube-addon-manager in a pod 2016-05-06 11:01:06 -07:00

README.md

addon-manager

The addon-manager periodically checks for Kubernetes manifest changes in the /etc/kubernetes/addons directory, and when there's a new or changed addon, the addon-manager automatically kubectl creates it.

It supports ReplicationControllers, Deployments, DaemonSets, ConfigMaps, Services, PersistentVolumes and PersistentVolumeClaims.

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