k3s/cluster/addons
Kubernetes Submit Queue cc28936bd1 Merge pull request #42771 from timstclair/fluentd
Automatic merge from submit-queue (batch tested with PRs 42768, 42760, 42771, 42767)

Bump fluentd-gcp to 2.0.2

See https://github.com/kubernetes/contrib/pull/2457
2017-03-09 00:07:59 -08:00
..
addon-manager Bump addon-manager to v6.4-beta.1 2017-03-08 16:08:39 -08: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 Update addons yaml files. 2017-02-27 09:21:59 -05:00
dashboard Update addons yaml files. 2017-02-27 09:21:59 -05:00
dns Adds default kube-dns configmap 2017-03-08 15:47:32 -08:00
dns-horizontal-autoscaler Update addons yaml files. 2017-02-27 09:21:59 -05: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 Fix username case in OWNERS files 2017-03-07 16:45:40 -08:00
fluentd-gcp Bump fluentd-gcp to 2.0.2 2017-03-08 17:20:32 -08:00
node-problem-detector Merge pull request #41949 from Random-Liu/collect-npd-log 2017-03-01 04:10:08 -08: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 Adds the new addon-manager labels on cluster addon templates 2017-02-24 16:53:12 -08:00
registry Adds the new addon-manager labels on cluster addon templates 2017-02-24 16:53:12 -08:00
storage-class Merge pull request #41854 from vmware/default-storage-class.kerneltime 2017-02-25 05:02:52 -08: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.

Analytics