Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A Docker image for Kibana designed to work with Kubernetes logging #2013

Merged
merged 1 commit into from
Oct 28, 2014

Conversation

satnam6502
Copy link
Contributor

This pull request contains the source for a special Kibana Docker image which is set up to work with Elasticsearch and Kibana in separate pods or in the same pod.

# http://$ELASTICSEARCH_SERVICE_HOST:$ELASTICSEARCH_SERVICE_PORT:9200/XXX
# The proxy configuration occurs in a location block of the nginx configuration
# file /etc/nginx/sites-available/default.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Start the script with the following to ensure uncaught errors will break the script:

set -o errexit
set -o nounset
set -o pipefail

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done.

@filbranden
Copy link
Contributor

Some nitpicks but otherwise looks good.

@satnam6502 satnam6502 force-pushed the kibana-image branch 2 times, most recently from 7d20317 to f568e20 Compare October 28, 2014 21:19
@satnam6502
Copy link
Contributor Author

Thank you kindly @filbranden for your help. I think I have implemented all of your excellent suggestions.

filbranden added a commit that referenced this pull request Oct 28, 2014
A Docker image for Kibana designed to work with Kubernetes logging
@filbranden filbranden merged commit dfd7ef3 into kubernetes:master Oct 28, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants