github/kubernetes
4
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
Files
b625fea27e26f70c81109968ed5d1dfaeae08d0e
kubernetes/cluster/addons/addon-manager/README.md
Fabian Deutsch f6ee79b2ec addonManager: Add note about labeling 
The cluster manager is only picking up addons if they are labeled correctly.
2017-02-14 15:43:47 +01:00

1.3 KiB
Raw Blame History

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 requirement is to label them with kubernetes.io/cluster-service: "true".

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

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

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

Analytics