Commit Graph

9 Commits (6f85bd0c661ce044804e037736cc14abee15b74c)

Author SHA1 Message Date
Piotr Szczesniak e92192d379 Added new command clusterinfo to kubectl
This is first version of the command. It prints IPs of master and cluster
services. Should be improved once generalized labels are implemented #341.

It requires label kubernet.io/cluster-service=true set for cluster services.

Follow up cl after discussion in #4417.
2015-03-03 20:14:24 +01:00
rsokolowski b05274e237 Update skydns's etcd to version 2.0.3 2015-02-25 18:22:23 +01:00
Tim Hockin fcfe420685 Add cluster-service label to DNS
Also rename the rc, pod, and service, which I have meant to do for a long time.
2015-02-19 14:15:48 -08:00
Tim Hockin 61293afad6 better DNS docs 2015-01-22 12:18:25 -08:00
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
Joe Beda d20b9d4567 Merge pull request #3666 from thockin/golang-static
Fix static builds in go1.4
2015-01-21 10:07:41 -08:00
Tim Hockin 0a538132cf Fix static builds in go1.4
https://github.com/golang/go/issues/9344
2015-01-20 21:04:04 -08:00
Tim Hockin 2367360321 Update DNS doc 2015-01-17 19:42:09 -08:00
Joe Beda 6df6aab077 Move DNS from contrib to cluster/addons
This fixes #3190.
2015-01-05 12:32:35 -08:00