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 77ca1af895
Merge pull request #57455 from kawych/fix_metadata_agent 
Automatic merge from submit-queue (batch tested with PRs 54680, 59388, 57455). 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>.

Fix RBAC permissions for metadata agent.

**What this PR does / why we need it**:
Allows Stackdriver Metadata Agent to watch nodes and pods

**Release note**:
```release-note
Fix RBAC permissions for Stackdriver Metadata Agent.
```
 		2018-02-06 06:40:34 -08:00
..
addon-manager bump addon version in makefile 2018-01-17 12:53:27 -05:00
calico-policy-controller Update cluster addon Calico to v2.6.6 2018-01-18 17:05:16 -06:00
cluster-loadbalancing Update defaultbackend image to 1.4 and deployment apiVersion to apps/v1 2018-01-05 11:09:54 +08:00
cluster-monitoring cluster/gce: remove salt comments from manifests 2018-02-01 08:39:56 -08:00
dashboard Ensure that the runtime mounts RO volumes read-only 2018-02-01 10:02:29 -07:00
device-plugins/nvidia-gpu Update nvidia-gpu-device-plugin addon. 2017-12-12 20:53:27 -08:00
dns Revert "Add self anti-affinity to kube-dns pods" 2018-02-05 18:24:23 +01:00
dns-horizontal-autoscaler Fix autoscaler deployment bug 2018-01-21 19:18:14 +08:00
etcd-empty-dir-cleanup sync code from copy destination 2018-01-20 14:48:33 +08:00
fluentd-elasticsearch fix typo in cluster 2018-02-03 11:08:06 +08:00
fluentd-gcp Remove salt configuration from the fluentd-gcp configuration. 2018-01-22 21:06:09 -08:00
ip-masq-agent Revert k8s.gcr.io vanity domain 2017-12-22 14:36:16 -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 Bump metadata proxy to v1.9 2018-01-19 15:24:30 -08:00
metrics-server Merge pull request #58162 from kawych/get_rights 2018-01-24 17:41:33 -08:00
node-problem-detector Revert k8s.gcr.io vanity domain 2017-12-22 14:36:16 -08:00
python-image Revert k8s.gcr.io vanity domain 2017-12-22 14:36:16 -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