github/kubernetes
4
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
01026886e6
kubernetes/cluster/addons
History
Kubernetes Submit Queue db2ba2900b Merge pull request #41854 from vmware/default-storage-class.kerneltime 
Automatic merge from submit-queue (batch tested with PRs 41854, 41801, 40088, 41590, 41911)

Default storage class for vSphere Fixes #40070

**What this PR does / why we need it**:

Create default storage class for vSphere. This is part of the storage class GA effort https://github.com/kubernetes/features/issues/36

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

fixes #40070

**Special notes for your reviewer**:

**Release note**:

```release-note
```
2017-02-25 05:02:52 -08:00
..
addon-manager Bumps addon-manager to v6.4-alpha.3 and updates template files 2017-02-24 16:52:31 -08:00
calico-policy-controller Adds the new addon-manager labels on cluster addon templates 2017-02-24 16:53:12 -08:00
cluster-loadbalancing Adds the new addon-manager labels on cluster addon templates 2017-02-24 16:53:12 -08:00
cluster-monitoring Adds the new addon-manager labels on cluster addon templates 2017-02-24 16:53:12 -08:00
dashboard Adds the new addon-manager labels on cluster addon templates 2017-02-24 16:53:12 -08:00
dns Adds the new addon-manager labels on cluster addon templates 2017-02-24 16:53:12 -08:00
dns-horizontal-autoscaler Adds the new addon-manager labels on cluster addon templates 2017-02-24 16:53:12 -08: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 Adds the new addon-manager labels on cluster addon templates 2017-02-24 16:53:12 -08:00
fluentd-gcp Adds the new addon-manager labels on cluster addon templates 2017-02-24 16:53:12 -08:00
node-problem-detector Adds the new addon-manager labels on cluster addon templates 2017-02-24 16:53:12 -08: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 Adds the new addon-manager labels on cluster addon templates 2017-02-24 16:53:12 -08:00
registry Adds the new addon-manager labels on cluster addon templates 2017-02-24 16:53:12 -08:00
storage-class Merge pull request #41854 from vmware/default-storage-class.kerneltime 2017-02-25 05:02:52 -08:00
BUILD Build release tarballs in bazel and add make bazel-release rule 2017-01-13 16:17:44 -08: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