github
/
k3s
mirror of https://github.com/k3s-io/k3s
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
k3s/cluster/addons/addon-manager
History
Zihong Zheng c449ef8a25 Added CHANGELOG to addon manager 2016-10-27 12:31:19 -07:00
..
CHANGELOG.md Added CHANGELOG to addon manager 2016-10-27 12:31:19 -07:00
Dockerfile addon-manager: remove `kube-addon-update.sh` from Dockerfile 2016-10-21 15:47:31 -07:00
Makefile increment kube-addon-manager version number; 2016-10-26 14:38:51 -07:00
README.md Updated addon manager READMEs 2016-10-17 21:10:12 -07:00
kube-addons.sh Upgrade addon-manager with kubectl apply 2016-10-11 16:22:02 -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 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