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 7ef11bd964
Merge pull request #59237 from tanshanshan/addons1 
Automatic merge from submit-queue (batch tested with PRs 59767, 56454, 59237, 59730, 55479). If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>.

Change critical pods’ template to use priority

**What this PR does / why we need it**:
Change critical pods’ template to use priority
Thanks.
**Which issue(s) this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close the issue(s) when PR gets merged)*:
ref #57471

**Special notes for your reviewer**:

**Release note**:

```release-note

```
 		2018-02-12 15:44:36 -08:00
..
addon-manager Switch to k8s.gcr.io vanity domain 2018-02-07 21:14:19 -08:00
calico-policy-controller Merge pull request #59237 from tanshanshan/addons1 2018-02-12 15:44:36 -08:00
cluster-loadbalancing Switch to k8s.gcr.io vanity domain 2018-02-07 21:14:19 -08:00
cluster-monitoring Merge pull request #59237 from tanshanshan/addons1 2018-02-12 15:44:36 -08:00
dashboard Merge pull request #59237 from tanshanshan/addons1 2018-02-12 15:44:36 -08:00
device-plugins/nvidia-gpu Switch to k8s.gcr.io vanity domain 2018-02-07 21:14:19 -08:00
dns Merge pull request #59237 from tanshanshan/addons1 2018-02-12 15:44:36 -08:00
dns-horizontal-autoscaler Merge pull request #59237 from tanshanshan/addons1 2018-02-12 15:44:36 -08:00
etcd-empty-dir-cleanup Merge pull request #59237 from tanshanshan/addons1 2018-02-12 15:44:36 -08:00
fluentd-elasticsearch Merge pull request #59237 from tanshanshan/addons1 2018-02-12 15:44:36 -08:00
fluentd-gcp Merge pull request #59237 from tanshanshan/addons1 2018-02-12 15:44:36 -08:00
ip-masq-agent Merge pull request #59237 from tanshanshan/addons1 2018-02-12 15:44:36 -08:00
kube-proxy Add wildcard tolerations to kube-proxy. 2017-11-29 12:36:58 -08:00
metadata-agent Fix RBAC permissions for metadata agent. 2018-02-06 13:47:37 +01:00
metadata-proxy Merge pull request #59237 from tanshanshan/addons1 2018-02-12 15:44:36 -08:00
metrics-server Merge pull request #59237 from tanshanshan/addons1 2018-02-12 15:44:36 -08:00
node-problem-detector Switch to k8s.gcr.io vanity domain 2018-02-07 21:14:19 -08:00
python-image Switch to k8s.gcr.io vanity domain 2018-02-07 21:14:19 -08:00
rbac gce: split legacy kubelet node role binding and bootstrapper role binding 2017-12-13 21:56:18 -05:00
storage-class [addon/storage-class] update storageclass groupversion in storage-class 2017-10-22 19:50:47 +08:00
BUILD Use the pkg_tar wrapper from kubernetes/repo-infra 2018-01-18 17:10:16 -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