kubernetes/cluster/addons
Jingyuan Liang 4dfc684b34 Set kube-proxy memory request to 50Mi
With optional override using KUBE_PROXY_MEMORY_REQUEST following the
KUBE_PROXY_CPU_REQUEST pattern.
2023-05-26 01:01:33 +00:00
..
addon-manager add changelog for kube-addon-manager v9.1.7 2023-05-15 09:39:45 +08:00
calico-policy-controller cleanup psp related rbac in cluster addons 2022-10-31 11:29:20 +08:00
cloud-controller-manager Split run controllers per controller-manager 2023-02-08 14:40:04 +00:00
cluster-loadbalancing Move from k8s.gcr.io to registry.k8s.io 2022-05-31 10:16:53 -04:00
device-plugins/nvidia-gpu Move from k8s.gcr.io to registry.k8s.io 2022-05-31 10:16:53 -04:00
dns remove nodes resource from CoreDNS RBAC manifest 2023-04-21 15:10:31 +02:00
dns-horizontal-autoscaler Move from k8s.gcr.io to registry.k8s.io 2022-05-31 10:16:53 -04:00
fluentd-gcp Move from k8s.gcr.io to registry.k8s.io 2022-05-31 10:16:53 -04:00
ip-masq-agent cleanup psp related rbac in cluster addons 2022-10-31 11:29:20 +08:00
kube-proxy Set kube-proxy memory request to 50Mi 2023-05-26 01:01:33 +00:00
metadata-agent cleanup psp related rbac in cluster addons 2022-10-31 11:29:20 +08:00
metadata-proxy cleanup psp related rbac in cluster addons 2022-10-31 11:29:20 +08:00
metrics-server Merge pull request #117121 from dgrisonnet/ms-15s-resolution 2023-04-11 20:21:45 -07:00
node-problem-detector cleanup psp related rbac in cluster addons 2022-10-31 11:29:20 +08:00
rbac Merge pull request #113267 from hoskeri/cleanup-kubelet-admin-role 2022-12-09 14:33:33 -08:00
storage-class Remove AWS legacy cloud provider + EBS in-tree storage plugin 2023-03-06 14:01:15 +00:00
volumesnapshots Update sidecar controllers to latest versions in the e2e 2022-09-29 22:13:11 +05:30
OWNERS Check in OWNERS modified by update-yamlfmt.sh 2021-12-09 21:31:26 -05:00
README.md Removed broken link to Analytics 2020-08-13 16:03:37 -04:00

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.