kubernetes

History

Sean McGinnis be131457ef Remove stale analytics links from docs Many README files and other docs contained a link to a an appspot tracking app that is no longer active. Following the links leads to an error about Go 1.9 no longer being supported. Go 1.9 support was dropped in appspot in 2019 and disabled June 2020. This also resulted in a broken image link displaying when viewing these files on GitHub. Since the app is no longer functioning, and since it causes a potentially (but granted, minor) confusing error to display, this just removes those links as I don't believe they are needed anymore. Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>		2020-11-18 07:04:48 -06:00
..
CHANGELOG.md	Remove stale analytics links from docs	2020-11-18 07:04:48 -06:00
Dockerfile	Fix kube-addon-manager overwriting resources with EnsureExists	2020-09-24 21:26:56 +00:00
kube-addons-main.sh	Fix kube-addon-manager overwriting resources with EnsureExists	2020-09-24 21:26:56 +00:00
kube-addons-test.sh	Fix kube-addon-manager overwriting resources with EnsureExists	2020-09-24 21:26:56 +00:00
kube-addons.sh	Fix kube-addon-manager overwriting resources with EnsureExists	2020-09-24 21:26:56 +00:00
Makefile	Update addon-manager makefile to use the new staging repo - for real	2020-10-01 15:39:25 -07:00
OWNERS	Migrate OWNERS file to apply the area/provider/gcp label	2019-12-04 17:05:43 -08:00
README.md	Removed broken link to Analytics	2020-08-13 16:03:37 -04:00

README.md

Addon-manager

addon-manager manages two classes of addons with given template files in $ADDON_PATH (default /etc/kubernetes/addons/).

Addons with label addonmanager.kubernetes.io/mode=Reconcile will be periodically reconciled. Direct manipulation to these addons through apiserver is discouraged because addon-manager will bring them back to the original state. In particular:
- Addon will be re-created if it is deleted.
- Addon will be reconfigured to the state given by the supplied fields in the template file periodically.
- Addon will be deleted when its manifest file is deleted from the $ADDON_PATH.
Addons with label addonmanager.kubernetes.io/mode=EnsureExists will be checked for existence only. Users can edit these addons as they want. In particular:
- Addon will only be created/re-created with the given template file when there is no instance of the resource with that name.
- Addon will not be deleted when the manifest file is deleted from the $ADDON_PATH.

Notes:

Label kubernetes.io/cluster-service=true is deprecated (only for Addon Manager). In future release (after one year), Addon Manager may not respect it anymore. Addons have this label but without addonmanager.kubernetes.io/mode=EnsureExists will be treated as "reconcile class addons" for now.
Resources under $ADDON_PATH need to have either one of these two labels. Otherwise it will be omitted.

Images

addon-manager images are pushed to k8s.gcr.io. As addon-manager is built for multiple architectures, there is an image per architecture in the format - k8s.gcr.io/kube-addon-manager-$(ARCH):$(VERSION).

How to release

The addon-manager is built for multiple architectures.

Change something in the source
Bump VERSION in the Makefile
Bump KUBECTL_VERSION in the Makefile if required
Build the amd64 image and test it on a cluster
Push all images

# Build for linux/amd64 (default)
$ make push ARCH=amd64
# ---> staging-k8s.gcr.io/kube-addon-manager-amd64:VERSION
# ---> staging-k8s.gcr.io/kube-addon-manager:VERSION (image with backwards-compatible naming)

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

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

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

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

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