8e5b17cf13
Signed-off-by: Mrunal Patel <mrunalp@gmail.com> |
||
---|---|---|
.. | ||
CHANGELOG.md | ||
Dockerfile | ||
kube-addons.sh | ||
Makefile | ||
namespace.yaml | ||
README.md |
addon-manager
The addon-manager
periodically kubectl apply
s 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
- Change something in the source
- Bump
VERSION
in theMakefile
- Bump
KUBECTL_VERSION
in theMakefile
if required - Build the
amd64
image and test it on a cluster - 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