Fluentd to Elasticsearch image

This pull request is for the sources needed to make the google/fluentd-elasticsearch image which is invoked by the manifest pod specification file which is installed when the user gives the --fluentd-es flag during cluster turn up to ask for this logging option.
On Tue, Oct 14, 2014 at 11:52 PM, Johan Euphrosine
<notifications@github.com> wrote:
>
> In contrib/logging/fluentd-es-image/run.sh:
>
> > +# you may not use this file except in compliance with the License.
> > +# You may obtain a copy of the License at
> > +#
> > +#     http://www.apache.org/licenses/LICENSE-2.0
> > +#
> > +# Unless required by applicable law or agreed to in writing, software
> > +# distributed under the License is distributed on an "AS IS" BASIS,
> > +# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> > +# See the License for the specific language governing permissions and
> > +# limitations under the License.
> > +
> > +# WARNING! HORRIBLE HACK! We expect /outerhost to be mapped to
> > +# the enclosing /etc/host file so we can determine the name of
> > +# the host machine (super fragile). This is a temporary hack until
> > +# service IPs are done.
> > +OUTER_HOST=`tail -n 1 /outerhost | awk '{print $3}'`
>
> The gateway worked worked for my bootstrap hack:
> https://github.com/GoogleCloudPlatform/kubernetes/pull/1716/files#diff-14da3738142f38850fb7acf7aafb6f80R18

Interesting - I could not make it work.  Either way it's almost moot.
ip-per-service should go in today, DNS soon after.

> @thockin when you say you don't want coupling with the outer host, can you expand a little bit more? Do you expect the ip of the kubelet managing a given pod to change during the lifetime of the container?

Maybe.  Consider live migration, which I know some people have started
to make work.