Commit Graph

20 Commits (835a87aed2478ee441f2dbfab15124315ddd880a)

Author SHA1 Message Date
Satnam Singh cfb8577324 Update Kibana to v1.2 which paramaterizes location of Elasticsearch 2015-04-03 14:55:00 -07:00
Jon Langemak 35038dc19a Added ES ENV variables so Kibana can be access in other ways 2015-04-02 21:58:10 -05:00
Jeff Lowdermilk 506887515d Rename google-containers to google_containers in image names 2015-04-01 09:16:48 -07:00
Satnam Singh 73a9ab2928 Rename logging image to use google_containers 2015-03-31 16:00:52 -07:00
Jeff Lowdermilk bec982774b Merge pull request #6038 from satnam6502/fluentd-es-image
Create a gcr.io image for Flunentd to Elasticsearch node level logging
2015-03-27 09:05:00 -07:00
Satnam Singh 19e621c951 Create a gcr.io image for Flunentd to Elasticsearch node level logging 2015-03-26 21:07:15 -07:00
Jeff Lowdermilk 2b71857816 Pull cluster addon images from gcr.io 2015-03-26 19:59:27 -07:00
Satnam Singh 985d5c1f95 Add a prefix to the POS file for Fluentd to Elasticsearch 2015-03-17 13:13:03 -07:00
Satnam Singh 3ce0ede78e Modify Fluentd to ES setup to pass flags 2015-03-10 10:11:26 -07:00
Satnam Singh 2486de1287 Change Fluentd config to read from head of Docker container logs 2015-03-09 23:25:52 -07:00
Satnam Singh 72183c064c Use proxy instead of load balancer 2015-03-02 13:44:41 -08:00
Tim Hockin e0e6741027 Stop using named ports in examples and scripts. 2015-03-01 21:30:45 -08:00
Satnam Singh eda8a676f4 Make a Kubernetes specific version of an Elasticsearch Docker container 2015-02-23 18:41:56 -08:00
Zach Loafman ea5d2f99ae Merge pull request #4622 from satnam6502/cluster-logging
Update cluster logging documentation to use kubectl for public IPs
2015-02-23 09:57:46 -08:00
Satnam Singh df2dfd6695 Add kubernetes.io/cluster-service label to cluster level logging services 2015-02-19 16:03:41 -08:00
Satnam Singh b2fcb14db1 Update cluster logging documentation to use kubectl for obtaining the public IPs 2015-02-19 14:05:16 -08:00
Zach Loafman ae27f29c56 Reinstate cluster logging URLs to the end of kube-up.sh
Adds labels to the services, waits for them to be created (which
should be instant, but just in case), query the forwarding rules like
as we did before.

Fixes #3893
2015-02-03 08:27:02 -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
Satnam Singh cd5a44e381 Remove curl check from Kibana image 2015-01-14 21:32:29 -08:00
Satnam Singh 295bd3768d Launch Elasticsearch and Kibana automatically 2015-01-09 13:41:46 -08:00