History

Kubernetes Submit Queue b41e415ebd Merge pull request #43137 from shashidharatd/federation-domain Automatic merge from submit-queue [Federation] Remove FEDERATIONS_DOMAIN_MAP references Remove all references to FEDERATIONS_DOMAIN_MAP as this method is no longer is used and is replaced by adding federation domain map to kube-dns configmap. cc @madhusudancs @kubernetes/sig-federation-pr-reviews Release note: ``` [Federation] Mechanism of adding `federation domain maps` to kube-dns deployment via `--federations` flag is superseded by adding/updating `federations` key in `kube-system/kube-dns` configmap. If user is using kubefed tool to join cluster federation, adding federation domain maps to kube-dns is already taken care by `kubefed join` and does not need further action. ```		2017-04-06 02:05:42 -07:00
..
addon-manager	Merge pull request #42668 from ixdy/build-silence-docker-rmi	2017-03-30 23:36:24 -07:00
calico-policy-controller	Adds the new addon-manager labels on cluster addon templates	2017-02-24 16:53:12 -08:00
cluster-loadbalancing	Merge pull request #42212 from timstclair/defaultbackend	2017-03-01 15:30:40 -08:00
cluster-monitoring	Add stackdriver monitoring option	2017-03-27 12:10:04 +02:00
dashboard	Update dashboard to version 1.6	2017-03-16 16:15:48 +01:00
dns	Remove FEDERATIONS_DOMAIN_MAP references	2017-03-15 23:06:16 +05:30
dns-horizontal-autoscaler	Merge pull request #42617 from MrHohn/dns-autoscaler-rbac	2017-03-29 15:43:10 -07:00
e2e-rbac-bindings	Adds the new addon-manager labels on cluster addon templates	2017-02-24 16:53:12 -08:00
etcd-empty-dir-cleanup	Bump etcd-empty-dir-cleanup to 3.0.14.0	2017-02-22 13:22:04 -08:00
fluentd-elasticsearch	Remove toleration from fluentd-elasticsearch	2017-04-05 11:27:14 +02:00
fluentd-gcp	Merge pull request #43379 from crassirostris/fluentd-gcp-docs	2017-03-23 02:08:56 -07:00
node-problem-detector	Update NPD rbac.	2017-03-23 23:07:55 -07:00
podsecuritypolicies	default policy	2016-05-11 18:07:36 -04:00
python-image	Always --pull in docker build to ensure recent base images	2017-01-10 16:21:05 -08:00
rbac	Give apiserver full access to kubelet API	2017-03-17 18:05:19 -04:00
registry	Adds the new addon-manager labels on cluster addon templates	2017-02-24 16:53:12 -08:00
storage-class	Rename default storageclasses	2017-03-16 09:14:12 +01:00
BUILD	Build release tarballs in bazel and add `make bazel-release` rule	2017-01-13 16:17:44 -08:00
README.md	Updates READMEs regarding the new behavior of addon-manager	2017-02-24 16:42:41 -08:00

README.md

Cluster add-ons

Overview

Cluster add-ons are resources like Services and Deployments (with pods) that are shipped with the Kubernetes binaries and are considered an inherent part of the Kubernetes clusters.

There are currently two classes of add-ons:

Add-ons that will be reconciled.
Add-ons that will be created if they don't exist.

More details could be found in addon-manager/README.md.

Cooperating Horizontal / Vertical Auto-Scaling with "reconcile class addons"

"Reconcile" class addons will be periodically reconciled to the original state given by the initial config. In order to make Horizontal / Vertical Auto-scaling functional, the related fields in config should be left unset. More specifically, leave replicas in ReplicationController / Deployment / ReplicaSet unset for Horizontal Scaling, leave resources for container unset for Vertical Scaling. The periodic reconcile won't clobbered these fields, hence they could be managed by Horizontal / Vertical Auto-scaler.

Add-on naming

The suggested naming for most of the resources is <basename> (with no version number). Though resources like Pod, ReplicationController and DaemonSet are exceptional. It would be hard to update Pod because many fields in Pod are immutable. For ReplicationController and DaemonSet, in-place update may not trigger the underlying pods to be re-created. You probably need to change their names during update to trigger a complete deletion and creation.