This repository has been archived by the owner on May 16, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Readiness probe failing in ES chart 7.15.0 for images 7.16.0 & 7.16.1 #1473
Comments
I came here to post the same thing. I need to upgrade to 7.16.1 and cannot because of this readiness issue... |
Actually I see that this fix works: |
fixed by #1464 |
Is there a timeline to release a first version of this branch? I think at the moment quite a lot of people are willing to upgrade their elastic instances due to the log4j vulnerability... |
Even after the release of version 7.16.1, here it still gives the same bug reported in this issue. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Chart version:
7.15.0
Kubernetes version:
Kubernetes provider: E.g. GKE (Google Kubernetes Engine)
GKE
Helm Version:
Describe the bug:
Readiness probes failing with chart 7.15 and docker images 7.16.0 and 7.16.1
Steps to reproduce:
Expected behavior:
Provide logs and/or server output (if relevant):
Looks like the
[[
in the readiness probe script is not compatible with whatever/bin/sh
provides in the docker imageThe text was updated successfully, but these errors were encountered: