18 Commits (ba110e9f08e8d41584dc7cb1eafe9498c3781505)

Author	SHA1	Message	Date
Marcin Wielgus	46b0dc64f5	Reduce CPU scheduler request to 75m	2017-06-22 17:57:57 +02:00
David Ashpole	e223eb93b5	make all static system pods critical	2017-06-12 15:22:04 -07:00
Jordan Liggitt	cc11d7367a	Switch kube-scheduler to secure API access	2017-02-15 01:05:42 -05:00
Marcin Wielgus	11fabd7176	Scheduling algorithm provider flag in kube-up.sh	2016-08-22 17:49:00 +02:00
Jeff Lowdermilk	51198f59da	Add --feature-gates to kube-system components ... apiserver,scheduler,controller-manager,proxy,kubelet all get flag. Using one variable to plumb through config via salt/init scripts for GCE and GKE	2016-08-19 09:07:43 -07:00
Mike Danese	6d24ca487a	add labels to kube component static pods	2016-04-14 19:13:18 -07:00
Dawn Chen	54933902b2	Make master component pods burstable, instead of guaranteed.	2016-02-12 14:28:48 -08:00
gmarek	fc6247152b	Split levels of verbosity of test logging on components.	2015-12-28 11:41:09 +01:00
Mike Danese	4ace8280a0	add an option to push/pull component images from a registry using kube-up	2015-12-08 14:19:30 -08:00
Wojciech Tyczynski	2a74d1d6ca	Tweak limits in manifest files.	2015-10-05 14:45:43 +02:00
Justin Santa Barbara	0ff8dd45ef	Fix escaping problem in kube-scheduler manifest ... '{{pillar[log_level]}}' was appearing literally in the command line, instead of being substituted. Fixes #12787	2015-08-17 08:16:24 -04:00
Robert Bailey	8df33bc1a7	Register the kubelet on the master node with an apiserver. This option is ... separated from the apiserver running locally on the master node so that it can be optionally enabled or disabled as needed. Also, fix the healthchecking configuration for the master components, which was previously only working by coincidence: If a kubelet doesn't register with a master, it never bothers to figure out what its local address is. In which case it ends up constructing a URL like http://:8080/healthz for the http probe. This happens to work on the master because all of the pods are using host networking and explicitly binding to 127.0.0.1. Once the kubelet is registered with the master and it determines the local node address, it tries to healthcheck on an address where the pod isn't listening and the kubelet periodically restarts each master component when the liveness probe fails.	2015-08-06 13:39:32 -07:00
gmarek	5bb7eec5ab	Use salt pillars to pass test arguments during cluster creation.	2015-07-31 09:32:01 +02:00
Dawn Chen	9ce11545c0	Explicitly configure master component containers and nginx with 200m each.	2015-07-02 10:46:39 -07:00
nikhiljindal	274792d7bb	Stop exposing v1beta3 by default	2015-07-01 14:38:02 -07:00
Brendan Burns	ff3f463e00	Add liveness checks to the controller-manager and scheduler.	2015-06-09 13:06:04 -07:00
Abhishek Shah	96439b5a52	logs for master components	2015-04-29 09:51:09 -07:00
Abhishek Shah	a908bb78ea	kube-scheduler in a pod	2015-04-14 17:53:12 -07:00