github
/
k3s
mirror of https://github.com/k3s-io/k3s
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
30,088 Commits
32 Branches
881 Tags
633 MiB
Commit Graph

45 Commits (9f4e30ba88b4f5061bed681ac5f69836df145b4d)

Author SHA1 Message Date
Wojciech Tyczynski f6dc06bdc7 Always enable second etcd for events 2016-02-16 11:48:46 +01:00
Dawn Chen 54933902b2 Make master component pods burstable, instead of guaranteed. 2016-02-12 14:28:48 -08:00
Wojciech Tyczynski 38bb110905 Enable etcd for events only in large clusters 2015-12-18 12:03:29 +01:00
Joe Beda 993c1ee222 Update etcd to 2.2.1 2015-11-04 12:26:57 -08:00
Filip Grzadkowski c1345ce2d9 Merge pull request #15068 from wojtek-t/fix_default_limits 
Tweak limits for system pods in manifest files.
 2015-10-07 09:41:28 +02:00
Wojciech Tyczynski 2a74d1d6ca Tweak limits in manifest files. 2015-10-05 14:45:43 +02:00
Wojciech Tyczynski 0f1cbe37a4 Events in separate etcd 2015-10-05 10:54:24 +02:00
Abhishek Shah 2d3a688ab7 reduce cpu requirement for etcd, after 2 etcd pods are being run 2015-10-02 10:31:04 -07:00
Brendan Burns a4581c7cd5 Add a second etcd instance for use with events. 2015-09-29 13:13:59 -07:00
derekwaynecarr 360e7620d3 Move vagrant to flannel 2015-09-15 15:42:38 -04:00
CJ Cullen c77e800495 Add liveness probe for master's etcd pod 2015-08-25 10:37:00 -07: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
Victor Marmol dd37642369 Merge pull request #10488 from justinsb/salt_support_systemd 
Salt: support systemd (don't assume Redhat <=> systemd)
 2015-07-08 13:43:08 -07:00
Justin Santa Barbara bcd92c7522 Salt: support systemd (don't assume Redhat <=> systemd) 
Also work around problems with Salt & systemd services, in particular
that Salt doesn't issue a daemon-reload.
 2015-07-03 01:40:15 -04: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 ec1e308ae2 rev etcd to 2.0.12 2015-06-19 15:57:32 -07:00
Abhishek Shah fe906677d4 Etcd log mount 2015-06-08 17:21:11 -07:00
Filip Grzadkowski eecd7b8c0f Revert "Set GOMAXPROCS for etcd" 2015-05-13 17:53:04 +02:00
Filip Grzadkowski 7e8bde53dd Set GOMAXPROCS for etcd 2015-05-07 08:11:39 +02:00
Dawn Chen 8ede54c511 Upgrade kubernetes to gcr.io/google_containers/etcd:2.0.9 2015-04-07 16:26:11 -07:00
Abhishek Shah fb665ede4c Run etcd on localhost for all providers. 2015-04-03 14:00:44 -07:00
Abhishek Shah 23c42cd8b2 Etcd listens on localhost for GCE 2015-04-03 11:40:09 -07:00
Dawn Chen 814177c21b Using gcr.io/google_containers/etcd:2.0.8 2015-04-02 17:04:05 -07:00
Abhishek Shah 8e3a41b52c Run etcd 2.0.5 in a pod 2015-04-01 11:38:21 -07:00
Zach Loafman 848134fdfa Revert "Running etcd 2.0.5 in a pod on master" 2015-03-28 07:36:39 -07:00
Abhishek Shah 7750f35e7c Running etcd 2.0.5 in a pod on master 2015-03-27 17:50:10 -07:00
Satnam Singh 69f867dafb Upgrade etcd to v2.0.5 on the master 2015-03-23 13:52:04 -07:00
David Oppenheimer ba749284d0 Have etcd listen on all interfaces so that monit probes succeed. Closes #3852. 2015-02-19 23:14:14 -08:00
Justin SB 9a29d9f92a Etcd data dir must be empty 
Otherwise we get the error "unknown wal version in data dir /var/etcd"

When this is the homedir for etcd, e.g. .bashrc confuses it
 2015-02-02 08:09:32 -08:00
Satnam Singh db416c4f39 Merge pull request #3970 from justinsb/fix_aws 
aws cluster/kube-up.sh fixes
 2015-01-30 07:56:01 -08:00
derekwaynecarr aef084bf9d Various vagrant fixes, etcd 2.0 2015-01-30 00:15:34 -05:00
Brendan Burns a20ca78fb3 Update etcd to version 2.0.0 2015-01-29 17:53:53 -08:00
Justin Santa Barbara 51225c76da Apply jbeda's conditional tar fix 2015-01-29 20:35:36 -05:00
Joe Beda 7ee327146a Fix typo in initd scripts 2015-01-15 09:12:20 -08:00
Jernej Kos 430a04af45 Added missing Salt requisites. 2014-12-18 10:29:39 +01:00
Brendan Burns 927088de83 Fix etcd unpack by adding a explicit x flag. 2014-11-19 11:33:50 -08:00
Joe Beda d033dfcc2b Load etcd tarball from GCS. 
Also fix up comment about how to cache docker debs.
 2014-11-07 13:43:07 -08:00
Brendan Burns c4d6f3a1cd Fix the etcd md5 since they uploaded a new binary. 2014-10-29 11:18:37 -07:00
Joe Beda 15cd6f07d6 Use binary releases for cluster push scripts. 
This is for GCE right now.  Other clouds/clusters are probably broken.
 2014-10-10 12:30:11 -07:00
Brendan Burns 4a934427db Exclude vendored etcd. 2014-09-04 12:05:34 -07:00
Brendan Burns 3864cf453a Fix travis and cluster installs. 2014-09-04 10:31:09 -07:00
Filipe Brandenburger d7396acced Remove executable permissions of files that do not need it. 
In particular, .gitignore, *.go, *.sls and etcd.conf are files that
should not be marked as executable.

Tested: built it with hack/build-go.sh, called all binaries with
  the -version flag to confirm they work.

Signed-off-by: Filipe Brandenburger <filbranden@google.com>
 2014-08-01 08:22:46 -07:00
derekwaynecarr 69ae2fe4bb Initial vagrant setup and e2e testing support 2014-07-24 16:32:36 -04:00
Joe Beda 894a7e3282 Move everything out of src and reorganize scripts. 
Fixed up some scripts to be more robust.  Changed the e2e test setup to use g1-small instances.  Fixed up documentation to reflect the new script locations.  Disabled the "curl | bash" cluster launch as it hasn't been well tested and doesn't include the cloudcfg tool yet.
 2014-06-06 21:41:19 -07:00