605294108f
Automatic merge from submit-queue issue_43986: fix docu with non-functional proxy The documentation defines a couple of replication-controller and service to provision a docker-registry somewhere on the cluster and have it available by the name viz. A record of kube-registry.default.svc.<clustername>. On each node, http-proxies are placed as daemon-set with the kube-registry DNS name set as upstream, so that the registry is available on each host under endpoint localhost:5000 Because in the documentation, selector-identifiers are the same for "upstream" registry and proxies, the proxies themselves register under the service intended for the upstream and now have themselves as upstream under a different port, where connection attempts result in "connection refused". Adapting selectors to be unique as in this patch fixes the problem. **What this PR does / why we need it**: Patch fixes (cf. above) erroneous documentation. **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes # Fixes #43986 **Special notes for your reviewer**: Thank you for your consideration. **Release note**: ```release-note ```
Cluster add-ons
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.