Branch: master
Find file History
Latest commit a22763b Feb 15, 2019
Permalink
Type Name Latest commit message Commit time
..
Failed to load latest commit information.
addon-manager Merge pull request #73540 from rlenferink/patch-5 Feb 8, 2019
calico-policy-controller Updated OWNERS files to include link to docs Feb 4, 2019
cluster-loadbalancing Updated OWNERS files to include link to docs Feb 4, 2019
cluster-monitoring Fix incorrect influxdb yamle file Feb 14, 2019
dashboard Updated OWNERS files to include link to docs Feb 4, 2019
device-plugins/nvidia-gpu Update nvidia-gpu-device-plugin to apps/v1 and use RollingUpdate upda… May 25, 2018
dns-horizontal-autoscaler Updated OWNERS files to include link to docs Feb 4, 2019
dns Update deprecated links Feb 15, 2019
fluentd-elasticsearch Updated OWNERS files to include link to docs Feb 4, 2019
fluentd-gcp Updated OWNERS files to include link to docs Feb 4, 2019
ip-masq-agent Updated OWNERS files to include link to docs Feb 4, 2019
kube-proxy Updated OWNERS files to include link to docs Feb 4, 2019
metadata-agent Updated OWNERS files to include link to docs Feb 4, 2019
metadata-proxy Updated OWNERS files to include link to docs Feb 4, 2019
metrics-server Updated OWNERS files to include link to docs Feb 4, 2019
node-problem-detector Change add-on manifests to apps/v1 Dec 19, 2018
prometheus Updated OWNERS files to include link to docs Feb 4, 2019
rbac Grant permissions for batch/job to cluster-autoscaler Oct 16, 2018
runtimeclass Update deprecated links Feb 15, 2019
storage-class change default storage class annotation for all addons Sep 6, 2018
storage-crds Updated OWNERS files to include link to docs Feb 4, 2019
BUILD Update repo-infra, bazel-skylib, rules_docker, and rules_go dependencies Feb 13, 2019
README.md Updated cluster/addons readme to match and point to docs Oct 18, 2017

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.

Analytics