![]() Many README files and other docs contained a link to a an appspot tracking app that is no longer active. Following the links leads to an error about Go 1.9 no longer being supported. Go 1.9 support was dropped in appspot in 2019 and disabled June 2020. This also resulted in a broken image link displaying when viewing these files on GitHub. Since the app is no longer functioning, and since it causes a potentially (but granted, minor) confusing error to display, this just removes those links as I don't believe they are needed anymore. Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com> |
||
---|---|---|
.. | ||
addon-manager | ||
calico-policy-controller | ||
cluster-loadbalancing | ||
dashboard | ||
device-plugins/nvidia-gpu | ||
dns | ||
dns-horizontal-autoscaler | ||
fluentd-elasticsearch | ||
fluentd-gcp | ||
ip-masq-agent | ||
kube-proxy | ||
metadata-agent | ||
metadata-proxy | ||
metrics-server | ||
node-problem-detector | ||
rbac | ||
storage-class | ||
volumesnapshots | ||
BUILD | ||
OWNERS | ||
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.