Tomislav Tomašić

Hi @okkez . Expectation is to parse the application logs separately from outher system containers. I was looking some more into how to achieve this, and will try using annotations...

@okkez I have defined a custom annotation, with which I was hoping to retag the application pods. However, this is not working as expected. The config filters out/drops all application...

Thanks for the example, @okkez . I tried it out,l and it looks like the events coming from pods which do not have the annotation aren't being retagged with `system.*`...

> This repo docs do mention how to schedule Curator jobs. You just need to learn Curator enough, in order to create a configuration that will deliver what you need....

I should probably elaborate a bit. This is the old bash script scheduled in cron: > #!/bin/bash > rm logs/backup_indices.log > export DAYS=40 > export SNAPSHOT_NAME=snapshot-$(date -d -${DAYS}days +%Y-%m-%d) >...

$SNAPSHOT_NAME is dynamically generated during each script execution, by using the linux "date" command "date -d -${DAYS}days +%Y-%m-%d)". I don't think that this is a viable approach for setting a...

Additionaly, any tips on how to configure the elasticsearch keystore (which appears to be a requirement for configuring both GCS & AWS S3 access to store snapshots)? https://www.elastic.co/guide/en/elasticsearch/plugins/current/repository-gcs-usage.html https://www.elastic.co/guide/en/elasticsearch/plugins/current/repository-s3-client.html

@pires I will try to build my own image based on yours, the expanded image will create the "elasticsearch.keystore" keyfile, as described here: https://www.elastic.co/guide/en/elasticsearch/reference/6.3/secure-settings.html That way all my containers will...

I found your Dockerfile here, and modified mine accordingly: https://github.com/pires/docker-elasticsearch/blob/6.2.2_1/Dockerfile **Dockerfile:** ``` FROM quay.io/pires/docker-elasticsearch-kubernetes:6.2.2_1 # inital setup USER elasticsearch COPY gcs.client.default.credentials_file /tmp/ ENV PATH /elasticsearch/bin:$PATH WORKDIR /elasticsearch # Copy configuration...

Ok, I managed to build the image. I then created a canary deployment for a canary client node. It is failing thusly: ``` > kubectl logs es-client-canary-598c8f54f7-s47ms sh: error setting...