7 Commits (229833f2f423b564e9944908ce0a81d9fe66f1c6)

Author	SHA1	Message	Date
Tim Hockin	e9dd8a68f6	Revert k8s.gcr.io vanity domain ... This reverts commit eba5b6092a. Fixes https://github.com/kubernetes/kubernetes/issues/57526	2017-12-22 14:36:16 -08:00
Tim Hockin	eba5b6092a	Use k8s.gcr.io vanity domain for container images	2017-12-18 09:18:34 -08:00
foxish	a5b7591646	Remove namespaces from all examples.	2016-11-11 11:57:33 -08:00
Klaus Ma	326e30772a	Added namespace to Spark example.	2016-04-19 00:34:47 +08:00
Zach Loafman	6e2e7bd3b6	Bump Spark / Zeppelin to 1.5.2 / 0.5.6 tags ... From https://github.com/kubernetes/application-images/pull/5	2016-03-04 13:26:05 -08:00
Zach Loafman	f8b83a65da	Zeppelin: Compress the image by doing the build on a separate image ... Pull the tar through to the image we need it on. Addresses #17231	2015-11-17 14:51:16 -08:00
Zach Loafman	51817850ba	Zeppelin: Add Zeppelin image to Spark example ... This adds a very basic Zeppelin image that works with the existing Spark example. As can be seen from the documentation, it has a couple of warts: * It requires kubectl port-forward (which is unstable across long periods of time, at least for me, on this app, bug incoming). See * I needed to roll my own container (none of the existing containers exactly matched needs, or even built anymore against modern Zeppelin master, and the rest of the example is Spark 1.5). The image itself is *huge*. One of the further refinements we need to look at is how to possibly strip the Maven build for this container down to just the interpreters we care about, because the deps here are frankly ridiculous. This might be a case where, if possible, we might want to open an upstream request to build things dynamically, then use something like probably the cut the image down considerably. (This might already be possible, need to poke at whether you can late-bind interpreters later.)	2015-11-13 12:02:11 -08:00