iwita 445e0f60bf init-commit		5 年之前
..
addon-manager	445e0f60bf init-commit	5 年之前
calico-policy-controller	445e0f60bf init-commit	5 年之前
cluster-loadbalancing	445e0f60bf init-commit	5 年之前
dashboard	445e0f60bf init-commit	5 年之前
device-plugins	445e0f60bf init-commit	5 年之前
dns	445e0f60bf init-commit	5 年之前
dns-horizontal-autoscaler	445e0f60bf init-commit	5 年之前
fluentd-elasticsearch	445e0f60bf init-commit	5 年之前
fluentd-gcp	445e0f60bf init-commit	5 年之前
ip-masq-agent	445e0f60bf init-commit	5 年之前
kube-proxy	445e0f60bf init-commit	5 年之前
metadata-agent	445e0f60bf init-commit	5 年之前
metadata-proxy	445e0f60bf init-commit	5 年之前
metrics-server	445e0f60bf init-commit	5 年之前
node-problem-detector	445e0f60bf init-commit	5 年之前
rbac	445e0f60bf init-commit	5 年之前
storage-class	445e0f60bf init-commit	5 年之前
volumesnapshots	445e0f60bf init-commit	5 年之前
BUILD	445e0f60bf init-commit	5 年之前
README.md	445e0f60bf init-commit	5 年之前

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.

[]()