mirror of https://github.com/ceph/ceph-csi.git synced 2024-11-13 01:40:23 +00:00

History

Serguei Bezverkhi e9033989a0 vendor updates		2018-03-07 11:43:06 -05:00
..
addon-manager	vendor updates	2018-03-07 11:43:06 -05:00
calico-policy-controller	vendor updates	2018-03-07 11:43:06 -05:00
cluster-loadbalancing	vendor updates	2018-03-07 11:43:06 -05:00
cluster-monitoring	vendor updates	2018-03-07 11:43:06 -05:00
dashboard	vendor updates	2018-03-07 11:43:06 -05:00
device-plugins/nvidia-gpu	vendor updates	2018-03-07 11:43:06 -05:00
dns	vendor updates	2018-03-07 11:43:06 -05:00
dns-horizontal-autoscaler	vendor updates	2018-03-07 11:43:06 -05:00
etcd-empty-dir-cleanup	vendor updates	2018-03-07 11:43:06 -05:00
fluentd-elasticsearch	vendor updates	2018-03-07 11:43:06 -05:00
fluentd-gcp	vendor updates	2018-03-07 11:43:06 -05:00
ip-masq-agent	vendor updates	2018-03-07 11:43:06 -05:00
istio	vendor updates	2018-03-07 11:43:06 -05:00
kube-proxy	vendor files	2018-01-10 13:42:26 -05:00
metadata-agent	vendor updates	2018-03-07 11:43:06 -05:00
metadata-proxy	vendor updates	2018-03-07 11:43:06 -05:00
metrics-server	vendor updates	2018-03-07 11:43:06 -05:00
node-problem-detector	vendor updates	2018-03-07 11:43:06 -05:00
python-image	vendor updates	2018-03-07 11:43:06 -05:00
rbac	vendor files	2018-01-10 13:42:26 -05:00
storage-class	vendor files	2018-01-10 13:42:26 -05:00
BUILD	vendor updates	2018-03-07 11:43:06 -05:00
README.md	vendor files	2018-01-10 13:42:26 -05:00

README.md

Legacy Cluster add-ons

For more information on add-ons see the documentation.

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.