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

Kubernetes yaml templates or Helm chart #209

Closed
dkirrane opened this issue Dec 11, 2017 · 6 comments
Closed

Kubernetes yaml templates or Helm chart #209

dkirrane opened this issue Dec 11, 2017 · 6 comments
Labels
discuss General discussion threads, suggestions for improvements, etc. question

Comments

@dkirrane
Copy link

dkirrane commented Dec 11, 2017

Wondering if you have any K8s templates or Helm chart for standing up ELK with SearchGaurd in a Kubernetes cluster

@jemacom
Copy link

jemacom commented Dec 12, 2017

Hey @dkirrane I was about to suggest using kompose. But after testing it locally it fails since the docker-compose.yml uses build and context and the Kompose maintainers still on it.
Check this issue

@antoineco
Copy link
Collaborator

antoineco commented Dec 12, 2017

I think this is way beyond the scope of this project. Here is an excellent starting point for running ELK on Kubernetes:

https://github.com/pires/kubernetes-elasticsearch-cluster

You should be able to swap the images and get it running with Searchguard without problem.

@surajnarwade
Copy link

surajnarwade commented Dec 14, 2017

@jemacom , kompose issue is fixed now :)
Please download latest kompose release 1.6 for latest changes

@jemacom
Copy link

jemacom commented Dec 14, 2017

@surajnarwade I think am still facing some issues although am using the 1.6 release.

$kompose version                                               
1.6.0 (e4adfef)
$kompose up -v                                                 
DEBU Docker Compose version: 2                    
DEBU Opening compose files: docker-compose.yml    
DEBU [0/0] [elk]: EventType: 32                   
DEBU [0/0] [elasticsearch]: Adding                
DEBU [0/2] [kibana]: Adding                       
DEBU [0/2] [logstash]: Adding                     
WARN Unsupported root level networks key - ignoring 
WARN Unsupported networks key - ignoring          
WARN Unsupported depends_on key - ignoring        
FATA Error while deploying application: k.Transform failed: image key required within build parameters in order to build and push service 'elasticsearch'

Any thoughts on this ? Thanks.

@surajnarwade
Copy link

@jemacom you need to mention image key in your services in docker compose file. then kompose will build your image with that name, push it to registry and then your cluster will pull it and deploy :)

@antoineco antoineco added the discuss General discussion threads, suggestions for improvements, etc. label Dec 14, 2017
@antoineco
Copy link
Collaborator

I'm not sure how far you managed to get with that ELK on Kubernetes story, but I found the following Helm charts in the Kubernetes GitHub org:

All 3 charts use the same Docker images as we do in this project and seem easy to configure. In my opinion this is by far more elegant and maintainable than using Kompose.

I suggest you give it a shot. I will close this issue in a few days because Kubernetes is a very special beast that do not share much with our Compose setup, but I welcome further discussion if you need guidance.

herpiko pushed a commit to herpiko/docker-elk that referenced this issue Jun 9, 2019
Ensure time zone override applies to Logstash
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discuss General discussion threads, suggestions for improvements, etc. question
Projects
None yet
Development

No branches or pull requests

4 participants