github/kubernetes
4
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
f3b870400d
kubernetes/cluster/addons
History
Matt Matejczyk f3b870400d Allow typha-cpa to get apps/deployments 
Without this it fails after deployments were switched from
extensions to apps with
```
E0902 11:25:51.197420       1 reflector.go:283] github.com/kubernetes-incubator/cluster-proportional-autoscaler/pkg/autoscaler/k8sclient/k8sclient.go:96: Failed to watch *v1.Node: unknown (get nodes)
E0902 11:25:53.118490       1 reflector.go:283] github.com/kubernetes-incubator/cluster-proportional-autoscaler/pkg/autoscaler/k8sclient/k8sclient.go:96: Failed to watch *v1.Node: unknown (get nodes)
E0902 11:25:54.997493       1 reflector.go:283] github.com/kubernetes-incubator/cluster-proportional-autoscaler/pkg/autoscaler/k8sclient/k8sclient.go:96: Failed to watch *v1.Node: unknown (get nodes)
E0902 11:25:57.097423       1 reflector.go:283] github.com/kubernetes-incubator/cluster-proportional-autoscaler/pkg/autoscaler/k8sclient/k8sclient.go:96: Failed to watch *v1.Node: unknown (get nodes)
E0902 11:25:59.097417       1 reflector.go:283] github.com/kubernetes-incubator/cluster-proportional-autoscaler/pkg/autoscaler/k8sclient/k8sclient.go:96: Failed to watch *v1.Node: unknown (get nodes)
I0902 11:25:59.697325       1 k8sclient.go:221] Falling back to extensions/v1beta1, error using apps/v1: deployments.apps "calico-typha" is forbidden: User "system:serviceaccount:kube-system:typha-cpha" cannot get resource "deployments/scale" in API group "apps" in the namespace "kube-system"
E0902 11:25:59.699833       1 autoscaler_server.go:120] Update failure: the server could not find the requested resource
```

Ref. https://github.com/kubernetes/test-infra/pull/13709
2019-09-02 13:52:10 +02:00
..
addon-manager Adde 9.0.2 to CHANGELOG.md 2019-08-01 20:15:46 +02:00
calico-policy-controller Allow typha-cpa to get apps/deployments 2019-09-02 13:52:10 +02: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 feat: cleanup pod critical pod annotations feature 2019-08-09 08:41:23 +08:00
dashboard Merge pull request #80864 from jeefy/owner-updates 2019-08-19 02:53:30 -07:00
device-plugins/nvidia-gpu feat: cleanup pod critical pod annotations feature 2019-08-09 08:41:23 +08:00
dns Merge pull request #82093 from rajansandeep/reconcilecorednscm 2019-08-30 07:59:56 -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 #80912 from monotek/fluentd-elasticsearch 2019-08-20 23:05:16 -07:00
fluentd-gcp feat: cleanup pod critical pod annotations feature 2019-08-09 08:41:23 +08:00
ip-masq-agent feat: cleanup pod critical pod annotations feature 2019-08-09 08:41:23 +08:00
kube-proxy feat: cleanup pod critical pod annotations feature 2019-08-09 08:41:23 +08:00
metadata-agent delete all duplicate empty blanks 2019-02-23 10:28:04 +08:00
metadata-proxy feat: cleanup pod critical pod annotations feature 2019-08-09 08:41:23 +08:00
metrics-server feat: cleanup pod critical pod annotations feature 2019-08-09 08:41:23 +08:00
node-problem-detector Update NPD addon to use v0.7.1 2019-08-29 11:24:13 -07:00
prometheus feat: cleanup pod critical pod annotations feature 2019-08-09 08:41:23 +08:00
rbac Merge pull request #75638 from ramnar/bugfix_24thMarch 2019-06-20 06:54:49 -07: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