History

Mrunal Patel 8e5b17cf13 Switch to github.com/golang/dep for vendoring Signed-off-by: Mrunal Patel <mrunalp@gmail.com>		2017-01-31 16:45:59 -08:00
..
addon-manager	Switch to github.com/golang/dep for vendoring	2017-01-31 16:45:59 -08:00
calico-policy-controller	Switch to github.com/golang/dep for vendoring	2017-01-31 16:45:59 -08:00
cluster-loadbalancing	Switch to github.com/golang/dep for vendoring	2017-01-31 16:45:59 -08:00
cluster-monitoring	Switch to github.com/golang/dep for vendoring	2017-01-31 16:45:59 -08:00
dashboard	Switch to github.com/golang/dep for vendoring	2017-01-31 16:45:59 -08:00
dns	Switch to github.com/golang/dep for vendoring	2017-01-31 16:45:59 -08:00
dns-horizontal-autoscaler	Switch to github.com/golang/dep for vendoring	2017-01-31 16:45:59 -08:00
e2e-rbac-bindings	Switch to github.com/golang/dep for vendoring	2017-01-31 16:45:59 -08:00
etcd-empty-dir-cleanup	Switch to github.com/golang/dep for vendoring	2017-01-31 16:45:59 -08:00
fluentd-elasticsearch	Switch to github.com/golang/dep for vendoring	2017-01-31 16:45:59 -08:00
fluentd-gcp	Switch to github.com/golang/dep for vendoring	2017-01-31 16:45:59 -08:00
node-problem-detector	Switch to github.com/golang/dep for vendoring	2017-01-31 16:45:59 -08:00
podsecuritypolicies	Switch to github.com/golang/dep for vendoring	2017-01-31 16:45:59 -08:00
python-image	Switch to github.com/golang/dep for vendoring	2017-01-31 16:45:59 -08:00
registry	Switch to github.com/golang/dep for vendoring	2017-01-31 16:45:59 -08:00
storage-class	Switch to github.com/golang/dep for vendoring	2017-01-31 16:45:59 -08:00
BUILD	Switch to github.com/golang/dep for vendoring	2017-01-31 16:45:59 -08:00
README.md	Switch to github.com/golang/dep for vendoring	2017-01-31 16:45:59 -08:00

README.md

Cluster add-ons

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. The add-ons are visible through the API (they can be listed using kubectl), but direct manipulation of these objects through Apiserver is discouraged because the system will bring them back to the original state, in particular:

If an add-on is deleted, it will be recreated automatically.
If an add-on is updated through Apiserver, it will be reconfigured to the state given by the supplied fields in the initial config.

On the cluster, the add-ons are kept in /etc/kubernetes/addons on the master node, in yaml / json files. The addon manager periodically kubectl applys the contents of this directory. Any legit modification would be reflected on the API objects accordingly. Particularly, rolling-update for deployments is now supported.

Each add-on must specify the following label: kubernetes.io/cluster-service: true. Config files that do not define this label will be ignored. For those resources exist in kube-system namespace but not in /etc/kubernetes/addons, addon manager will attempt to remove them if they are attached with this label. Currently the other usage of kubernetes.io/cluster-service is for kubectl cluster-info command to recognize these cluster services.

The suggested naming for most types of resources is just <basename> (with no version number) because we do not expect the resource name to change. But resources like Pod , ReplicationController and DaemonSet are exceptional. As Pod updates may not change fields other than containers[*].image or spec.activeDeadlineSeconds and may not add or remove containers, it may not be sufficient during a major update. For ReplicationController, most of the modifications would be legit, but the underlying pods would not got re-created automatically. DaemonSet has similar problem as the ReplicationController. In these cases, the suggested naming is <basename>-<version>. When version changes, the system will delete the old one and create the new one (order not guaranteed).

Add-on update procedure

To update add-ons, just update the contents of /etc/kubernetes/addons directory with the desired definition of add-ons. Then the system will take care of:

Removing objects from the API server whose manifest was removed.
Creating objects from new manifests
Updating objects whose fields are legally changed.

Cooperating with Horizontal / Vertical Auto-Scaling

As all cluster add-ons will be 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, and leave resources for container unset for Vertical Scaling. The periodical update won't include these specs, which will be managed by Horizontal / Vertical Auto-scaler.