Merge pull request kubernetes-retired#1068 from mumoshu/toggle-metric…

…s-server

Allow toggling Metrics Server installation

Two fixes to 0.9.9 rc.3 (kubernetes-retired#1043)

* Fix inability to re-render credentials

Fixes kubernetes-retired#1042

* The best possible work-around to stabilize apiserver+controller-manager w/ metrics-server

Fixes kubernetes-retired#1039

Merge pull request kubernetes-retired#997 from martinssipenko/env

Load member .env file that is generated by etcdadm.

Merge pull request kubernetes-retired#996 from camilb/bump-kubernetes…

…-version

Bump kubernetes version to 1.8.2.

Merge pull request kubernetes-retired#981 from mumoshu/k8s-1.7.8

Bump the default Kubernetes version to v1.7.8-coreos.1

Merge pull request kubernetes-retired#886 from jpb/kube2iam-image

core: add kube2iam image repo and tag

Merge pull request kubernetes-retired#886 from jpb/kube2iam-image

core: add kube2iam image repo and tag

Merge pull request kubernetes-retired#871 from mumoshu/fix-release-ch…

…annel-for-node-pool

Fix node pool release channel

Plugin System (kubernetes-retired#791)

This is an initial implementation of the plugin system kubernetes-retired#509 as proposed in kubernetes-retired#751. Not all but most of knobs mentioned in the proposal except pre/post-cluster-creation validations are implemented.

Basically, it allows the user to define a set of customizations to various aspects of resources created and managed by kube-aws as a "kube-aws plugin" and reuse it.
The set of customizations is defined in a separate file other than a `cluster.yaml` for reusability.

More concretely, provide `<your project root>/plugins/<your-plugin-name>/plugin.yaml` like seen in test/integration/plugin_test.go to extend a kube-aws cluster from many aspects including:

- additional iam policy statements per node role(worker/controller/etcd)
- additional cfn stack template resources per stack(root/control-plane/node-pool)
- additional systemd units/custom files per node role(worker/controller/etcd)
- additional kubelet feature gates for worker kubelets
- additional node labels for worker/controller kubelets

and so on.

The new plugin system is not used to implement core features of kube-aws yet. Therefore, I believe we don't need to worry much about breaking things via this change.

At least one core feature implemented as a plugin is planned in the next version of kube-aws v0.9.9, as noted in our roadmap.

Changes:

* Plugin System: Add support for node labels

* Plugin System: Add support for feature gates

* plugin-system: Add support for k8s manifests and helm releases

* plugin-system: Add support for kube-apiserver server options

* plugin-system: Add support for custom files

* plugin-system: Add support for custom IAM policy statements

* Rename plugin/api to plugin/pluginapi to better differentiate what the api is for

* Move the test helper for plugin to a seperate go file

* Extract a type representing the file uploaded to a kube-aws node into a separate go file

* plugin-system: Seperate logics from api

* plugin-system: Separate cluster extensions by plugins from cluster and plugins

* plugin-system: More separation of api and logic

* plugin-system: Move apply-kube-aws-plugins script for easier merging with master

* plugin-system: Rename pluginapi to pluginmodel

* plugin-system: Remove unused types and files

* plugin-system: Comment about `values` in plugin.yaml

* Reliability improvement to cloud-config-controller
* Fix occasional kube-node-label, cfn-signal errors
* Fix install-kube-system and apply-kube-aws-plugins services to better scheduled in order without spamming journal

Merge pull request kubernetes-retired#739 from kubernetes-incubator/u…

…pdate-owners

Update OWNERS