github/kubernetes
4
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
e7b7c8bc10
kubernetes/cluster/addons
History
Vinay Bannai e7b7c8bc10 The default-http-backend for handling 404 pages will now point to 404 handler 
with prometheus integration and provides metrics related to requests per second
and the duration of responding to the requests for various percentile
groupings. Please check
https://github.com/kubernetes/ingress-gce/blob/master/cmd/404-server-with-metrics/README.md
for details about the 404-server-with-metrics.
2019-06-17 11:24:47 -07:00
..
addon-manager Merge pull request #76404 from MrHohn/addon-manager-9.1 2019-04-15 18:05:36 -07:00
calico-policy-controller Merge pull request #77690 from MrHohn/CPVA-0.7.0 2019-05-14 07:17:21 -07:00
cluster-loadbalancing The default-http-backend for handling 404 pages will now point to 404 handler 2019-06-17 11:24:47 -07:00
cluster-monitoring Addon resizer version 1.8.5 2019-05-27 15:12:29 +02:00
dashboard Merge pull request #72667 from jeefy/update-dashboard-owners 2019-05-11 00:46:12 -07:00
device-plugins/nvidia-gpu Fix a bug in the gpu device plugin where not all devices were registered. 2019-04-24 18:02:00 -07:00
dns add upstream to CoreDNS ConfigMap 2019-06-11 18:38:46 -04:00
dns-horizontal-autoscaler Bump cluster-proportional-autoscaler to 1.6.0 2019-05-09 11:25:12 -07:00
fluentd-elasticsearch Merge pull request #77765 from coffeepac/es-6.7.2 2019-05-11 17:20:10 -07:00
fluentd-gcp Bump image of event-exporter. 2019-05-13 16:27:25 +02:00
ip-masq-agent Add 198.51.100.0/24 to non-masq ranges. 2019-05-15 16:23:41 -07:00
kube-proxy Move test/e2e use to v1 APIs 2019-06-03 14:46:08 -04:00
metadata-agent delete all duplicate empty blanks 2019-02-23 10:28:04 +08:00
metadata-proxy Bump metadata-proxy image to v0.1.12 2019-05-02 11:57:52 -07:00
metrics-server Move test/e2e use to v1 APIs 2019-06-03 14:46:08 -04:00
node-problem-detector Use Node-Problem-Detector v0.6.3 on GCI 2019-04-05 11:08:24 -07:00
prometheus Merge pull request #72452 from SuperQ/patch-1 2019-06-17 02:40:11 -07:00
rbac use static token to authenticate glbc 2019-05-01 22:24:48 -07:00
storage-class Enable resize in default gce storageclass 2019-06-03 18:06:51 -07:00
BUILD Update repo-infra, bazel-skylib, rules_docker, and rules_go dependencies 2019-02-12 17:55:10 -08:00
README.md Updated cluster/addons readme to match and point to docs 2017-10-18 10:36:24 -04: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.

Analytics