Charts: Elastalert chart references unmaintained docker image

Created on 31 Jan 2018 · 8Comments · Source: helm/charts

Preface on the below - I'm not sure if maybe there's a reason the chart is referencing the image mentioned below. I know I can override and will be testing something more modern this week.

Is this a BUG REPORT or FEATURE REQUEST? (choose one):
Bug report

Which chart:
stable/elastalert

What happened:
This chart is currently using quay.io/pickledrick/elastalert:

image:
  # docker image
  repository: quay.io/pickledrick/elastalert
  # docker image tag
  tag: stable

pickledrick/elastalert hasn't been updated since November 17, 2017, and it's source repo claims it's no longer supported. The upstream github.com/Yelp/elastalert has had 20+ merges since then.

What you expected to happen:
Use a more up-to-date repo like https://hub.docker.com/r/bitsensor/elastalert/

lifecyclrotten

Source

jlk

👍1

Most helpful comment

I asked the yelp/elastalert folks to see if they'd maintain an "official" image. Will see if it goes anywhere...

jlk on 6 Feb 2018

👍4

All 8 comments

cc @pickledrick

I'm happy to send a PR on this after testing...

jlk on 31 Jan 2018

@jlk happy for it to go back to to original, I forked and tagged 'stable' as a requirement to get this PR through. I can't fully remember why but I think it's because this tag didn't exist at the time.

crocswearer on 31 Jan 2018

Aaah...yeah that makes sense.

jlk on 31 Jan 2018

Will ponder this for a day or so and update or close.

jlk on 31 Jan 2018

I asked the yelp/elastalert folks to see if they'd maintain an "official" image. Will see if it goes anywhere...

jlk on 6 Feb 2018

👍4

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

fejta-bot on 7 May 2018

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

fejta-bot on 6 Jun 2018

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

fejta-bot on 6 Jul 2018

Was this page helpful?

0 / 5 - 0 ratings