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 ca37d42048
Merge pull request #55728 from rajansandeep/kubeupcoredns 
Automatic merge from submit-queue. 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>.

Add CoreDNS as an optional addon in kube-up

**What this PR does / why we need it**:
This PR adds the option of installing CoreDNS as an addon instead of kube-dns in kube-up.

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

**Special notes for your reviewer**:

**Release note**:

```release-note
kube-up: Add optional addon CoreDNS. 
Install CoreDNS instead of kube-dns by setting CLUSTER_DNS_CORE_DNS value to 'true'.
```
 		2017-11-27 14:10:54 -08:00
..
addon-manager Merge branch 'master' into addon-manager 2017-11-14 09:36:20 +01:00
calico-policy-controller Add optional addon PSPs 2017-11-10 13:57:33 -08:00
cluster-loadbalancing Update OWNERS files for networking components 2017-08-03 11:08:54 -07:00
cluster-monitoring Merge pull request #56151 from kawych/heapster_deployment 2017-11-22 21:48:51 -08:00
dashboard update dashboard image version 2017-07-31 11:08:08 +08:00
device-plugins/nvidia-gpu Changes nvidia-gpu device plugin addon config settings: 2017-11-20 17:32:53 -08:00
dns create fn for dns manifests 2017-11-15 11:35:05 -05:00
dns-horizontal-autoscaler Merge kube-dns-autoscaler templates into a single file 2017-10-03 09:43:57 -07:00
etcd-empty-dir-cleanup Add optional addon PSPs 2017-11-10 13:57:33 -08:00
fluentd-elasticsearch Merge pull request #55400 from mrahbar/update_elasticsearch_kibana 2017-11-22 03:54:23 -08:00
fluentd-gcp Merge pull request #55950 from crassirostris/fluentd-gcp-setting-resources-fix 2017-11-22 05:21:25 -08:00
ip-masq-agent Add optional addon PSPs 2017-11-10 13:57:33 -08:00
kube-proxy Merge pull request #52003 from vfreex/mount-lib-modules 2017-10-25 11:38:36 -07:00
metadata-agent Add deployment for Stackdriver Metadata Agent with version and resource requirement controlled by env variable 2017-11-22 16:21:52 +01:00
metadata-proxy Pass pod name and namespace argss to prom-to-sd sidecar of metadata-proxy 2017-11-14 16:52:55 +01:00
metrics-server Adjust resources for Metrics Server 2017-10-31 10:42:00 +01:00
node-problem-detector Reorganize addon PodSecurityPolicies 2017-11-10 13:57:32 -08:00
python-image
…
rbac gce: readd kubelet-bootstrap to kubelet user 2017-11-14 13:46:08 -08:00
registry fix invalid url link 2017-08-24 18:50:14 +08:00
storage-class [addon/storage-class] update storageclass groupversion in storage-class 2017-10-22 19:50:47 +08:00
BUILD Run hack/update-bazel.sh to generate BUILD files 2017-08-02 18:33:25 -07: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