github/kubernetes
4
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
d87e700f9b
kubernetes/cluster/addons
History
Matt Matejczyk d87e700f9b Addon Manager: Fix bug in generate_prune_whitelist_flags 
The bug seems to be currently dormant but I managed to trigger it in
some manual tests.

When the bug is triggered it appends empty --prune-whitelist without any
value which in turn can capture the next flag and can cause addon
manager to fail.

E.g. when bug is not triggered the kubectl command looks like this

```
kubectl ... --prune-whitelist extensions/v1beta1/Ingress --recursive ...
```

When it's triggered it will be

```
kubectl ... --prune-whitelist --recursive ...
```

which will capture the --recursive flag and will make addon-manager to
fail as there are no yamls in the top directory.
2019-10-23 13:08:42 +02:00
..
addon-manager Addon Manager: Fix bug in generate_prune_whitelist_flags 2019-10-23 13:08:42 +02:00
calico-policy-controller Update Calico to v3.8.3 2019-10-14 13:49: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 Introduce sig-instrumentation aliases in OWNERS_ALISES and simplify OWNERS files 2019-10-10 14:04:20 +02:00
dashboard Rename dashboard-controller.yaml to dashboard-deployment.yaml 2019-10-15 13:55:06 +03:00
device-plugins/nvidia-gpu feat: cleanup pod critical pod annotations feature 2019-08-09 08:41:23 +08:00
dns Use latest node-cache version with stubdomain fix. 2019-10-09 23:11:44 -07:00
dns-horizontal-autoscaler Bump cluster proportional autoscaler to 1.7.1 2019-08-26 13:22:53 -07:00
fluentd-elasticsearch Merge pull request #80437 from webwurst/patch-1 2019-10-16 07:41:42 -07:00
fluentd-gcp Introduce sig-instrumentation aliases in OWNERS_ALISES and simplify OWNERS files 2019-10-10 14:04:20 +02:00
ip-masq-agent feat: cleanup pod critical pod annotations feature 2019-08-09 08:41:23 +08:00
kube-proxy Offical kubernetes dashboard should schedule to linux node 2019-09-22 08:08:04 +08:00
metadata-agent Introduce sig-instrumentation aliases in OWNERS_ALISES and simplify OWNERS files 2019-10-10 14:04:20 +02:00
metadata-proxy feat: cleanup pod critical pod annotations feature 2019-08-09 08:41:23 +08:00
metrics-server bump metrics server version o v0.3.6 2019-10-14 16:43:26 +02:00
node-problem-detector Update NPD addon to use v0.7.1 2019-08-29 11:24:13 -07:00
prometheus Bump addon-resizer to 1.8.6 2019-09-26 10:00:59 +02:00
rbac Add read-only rbac for csinodes to cluster-autoscaler 2019-09-06 17:38:48 +02:00
storage-class Merge pull request #75638 from ramnar/bugfix_24thMarch 2019-06-20 06:54:49 -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