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

12 Commits (9936f09b78f3c4fae09beda9df403fc6316bf5c4)

Author SHA1 Message Date
Zach Loafman a305269e18 Deferred creation of SkyDNS, monitoring and logging objects 
This implements phase 1 of the proposal in #3579, moving the creation
of the pods, RCs, and services to the master after the apiserver is
available.

This is such a wide commit because our existing initial config story
is special:

* Add kube-addons service and associated salt configuration:
** We configure /etc/kubernetes/addons to be a directory of objects
that are appropriately configured for the current cluster.
** "/etc/init.d/kube-addons start" slurps up everything in that dir.
(Most of the difficult is the business logic in salt around getting
that directory built at all.)
** We cheat and overlay cluster/addons into saltbase/salt/kube-addons
as config files for the kube-addons meta-service.
* Change .yaml.in files to salt templates
* Rename {setup,teardown}-{monitoring,logging} to
{setup,teardown}-{monitoring,logging}-firewall to properly reflect
their real purpose now (the purpose of these functions is now ONLY to
bring up the firewall rules, and possibly to relay the IP to the user).
* Rework GCE {setup,teardown}-{monitoring,logging}-firewall: Both
functions were improperly configuring global rules, yet used
lifecycles tied to the cluster. Use $NODE_INSTANCE_PREFIX with the
rule. The logging rule needed a $NETWORK specifier. The monitoring
rule tried gcloud describe first, but given the instancing, this feels
like a waste of time now.
* Plumb ENABLE_CLUSTER_MONITORING, ENABLE_CLUSTER_LOGGING,
ELASTICSEARCH_LOGGING_REPLICAS and DNS_REPLICAS down to the master,
since these are needed there now.

(Desperately want just a yaml or json file we can share between
providers that has all this crap. Maybe #3525 is an answer?)

Huge caveats: I've gone pretty firm testing on GCE, including
twiddling the env variables and making sure the objects I expect to
come up, come up. I've tested that it doesn't break GKE bringup
somehow. But I haven't had a chance to test the other providers.
 2015-01-21 12:25:50 -08:00
Tim Hockin 59164ca844 Make DNS an option for cluster turnup 2014-12-29 09:18:12 -08:00
Tim Hockin 47141f05c7 standard config opt names: logging 2014-11-25 17:41:53 -08:00
Tim Hockin 52ad94d766 standard config opt names: node monitoring 2014-11-25 17:39:28 -08:00
Pieter Noordhuis 1df6f9ce6a Use curl exclusively in vSphere deployment 
This fixes #2295.
 2014-11-11 17:22:02 -08:00
Pieter Noordhuis 5b22dd7631 Move customizations of /srv/salt to overlay 
Also see #1783.
 2014-10-29 11:30:09 -07:00
Pieter Noordhuis fa24face8c Add 'portal_net' parameter to pillar 
In preparation for #1402.
 2014-10-29 11:30:09 -07:00
Pieter Noordhuis 1152471db7 Split reactor files 
There now are reactor files to run highstate on:

* New nodes only
* Master nodes
* Minion nodes
 2014-10-29 11:30:09 -07:00
Pieter Noordhuis e90f98a52c Make vSphere scripts work for binary deploys 
Fixes #1732.
 2014-10-29 11:30:08 -07:00
Joe Beda 38d5906044 Clean up READMEs and broken stuff. 
Move all support for clouds that are broken with this change into an `icebox` directory.  We'll move that stuff back out as we fix it up.
 2014-10-10 12:33:36 -07:00
Pieter Noordhuis 65bb90ffef Update apiserver defaults template 
Set "cloud" grain to "vsphere".

The "minion_ips" grain doesn't seem to be used anymore.
 2014-08-25 15:20:19 -07:00
Pieter Noordhuis ad7f131a5b Deploy k8s to vSphere 2014-08-24 20:27:05 -07:00