github
/
k3s
mirror of https://github.com/k3s-io/k3s
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
k3s/cluster/addons
History
Kubernetes Submit Queue 6ed4bc7b97 Merge pull request #46828 from cblecker/links-update 
Automatic merge from submit-queue (batch tested with PRs 46718, 46828, 46988)

Update docs/ links to point to main site

**What this PR does / why we need it**:
This updates various links to either point to kubernetes.io or to the kubernetes/community repo instead of the legacy docs/ tree in k/k
Pre-requisite for #46813

**Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #

**Special notes for your reviewer**:

**Release note**:
```release-note
NONE
```

@kubernetes/sig-docs-maintainers @chenopis @ahmetb @thockin
 		2017-06-06 11:43:18 -07:00
..
addon-manager Merge pull request #42668 from ixdy/build-silence-docker-rmi 2017-03-30 23:36:24 -07:00
calico-policy-controller Move tolerations to PodSpec for calico-node.yaml. 2017-06-01 09:57:03 +08:00
cluster-loadbalancing Update docs/ URLs to point to proper locations 2017-06-05 22:13:54 -07:00
cluster-monitoring Add stackdriver monitoring option 2017-03-27 12:10:04 +02:00
dashboard Update dashboard-controller.yaml 2017-05-17 14:12:12 +02:00
dns Update kube-dns version to 1.14.2 2017-05-11 12:29:00 -07:00
dns-horizontal-autoscaler Bump cluster-proportional-autoscaler to 1.1.2 2017-06-01 14:23:43 -07:00
e2e-rbac-bindings Adds the new addon-manager labels on cluster addon templates 2017-02-24 16:53:12 -08:00
etcd-empty-dir-cleanup Bump etcd-empty-dir-cleanup to 3.0.14.0 2017-02-22 13:22:04 -08:00
fluentd-elasticsearch Update fluentd-es-ds.yaml 2017-05-29 19:09:57 +02:00
fluentd-gcp Merge pull request #46787 from crassirostris/fluentd-gcp-update 2017-06-06 01:53:40 -07:00
ip-masq-agent Merge pull request #46782 from dnardo/ip-masq-agent 2017-06-03 12:28:27 -07:00
metadata-proxy Adding a metadata proxy addon to gce 2017-05-31 16:23:11 -07:00
node-problem-detector Add generic NoExecute Toleration to NPD 2017-05-16 12:15:06 +02:00
podsecuritypolicies default policy 2016-05-11 18:07:36 -04:00
python-image Always --pull in docker build to ensure recent base images 2017-01-10 16:21:05 -08:00
rbac enable tls bootstrap in GCE/GKE 2017-06-01 09:17:32 -07:00
registry Update docs/ URLs to point to proper locations 2017-06-05 22:13:54 -07:00
storage-class Support running StatefulSetBasic e2e tests with local-up-cluster 2017-04-28 15:10:22 -04:00
BUILD Replace git_repository with http_archive and use ixdy's fork of bazel tools for pkg_tar 2017-05-03 10:13:06 -07:00
README.md Updates READMEs regarding the new behavior of addon-manager 2017-02-24 16:42:41 -08:00

README.md

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.

Analytics