Dockerize es-indices-clean script#741
Conversation
| @@ -1,4 +1,4 @@ | |||
| #!/bin/bash | |||
There was a problem hiding this comment.
bash is not in alpine
| @@ -1,6 +1,5 @@ | |||
| import elasticsearch | |||
| import curator | |||
| import logging | |||
|
For what purpose? Is usability improved by running the script inside the container? |
|
How do you want to run it as cronjob without container? jaegertracing/jaeger-kubernetes#40 |
isaachier
left a comment
There was a problem hiding this comment.
Personally, LGTM. @black-adder isn't in the office this week. Maybe @vprithvi or @yurishkuro can give this a final look.
yurishkuro
left a comment
There was a problem hiding this comment.
- the name of the Dockerhub repository might look better as
(jaeger-)es-index-cleaner - the
es_indices_clean.shlooks like an anti-pattern. It will runpip installinside the container every time, I think we should only do this once at build time. And there's no need to have a shell script in the first place since we're already running in a python container - just execute python with the.pyfile directly
It uses the same naming convention as other images.
Do you want to remove scrip altogether? I agree about pip. |
|
The script might be useful for users not on Kubernetes, but they should probably use a real cronjob or Jenkins, so IMO makes sense to delete it. |
There isn't really a convention. I I just think "es index cleaner" describes better what the image represents than "es indices clean".
The python script will still be available, I am just saying there's no reason for a shell script as well, especially because it does |
that yes, I didn't read it properly. I thought you want to remove jaeger prefix :/. I will rename it |
|
@yurishkuro image has been renamed and shell script removed. |
Signed-off-by: Pavol Loffay <ploffay@redhat.com>
c36a4d8 to
83c7a56
Compare
Resolves #740
Signed-off-by: Pavol Loffay ploffay@redhat.com