Skip to content
This repository has been archived by the owner on May 16, 2023. It is now read-only.

readinessProbe missing -k for curl #1725

Closed
davidishee opened this issue Nov 14, 2022 · 1 comment
Closed

readinessProbe missing -k for curl #1725

davidishee opened this issue Nov 14, 2022 · 1 comment

Comments

@davidishee
Copy link

Chart version:

Latest on master has the issue, but originally found on 7.16.3

https://github.com/elastic/helm-charts/blob/main/elasticsearch/templates/statefulset.yaml

a11730e

Kubernetes version:

v1.21.11+31d53a1

Kubernetes provider: E.g. GKE (Google Kubernetes Engine)

OpenShift

Helm Version:

3.3.4

helm get release output

e.g. helm get elasticsearch (replace elasticsearch with the name of your helm release)

Be careful to obfuscate every secrets (credentials, token, public IP, ...) that could be visible in the output before copy-pasting.

If you find some secrets in plain text in helm get release output you should use Kubernetes Secrets to managed them is a secure way (see Security Example).

Output of helm get release

Describe the bug:

Line 292 of the readinessProbe doesn't include -k so it fails if security is enabled.

https://github.com/elastic/helm-charts/blame/8565b30cde0c373bbd2812079c2114bfcf8ed524/elasticsearch/templates/statefulset.yaml#L292

Steps to reproduce:

  1. Deploy chart with security enabled (https)
  2. readiness probes fail

Expected behavior:

readiness probes succeed when security (https) is enabled.

Provide logs and/or server output (if relevant):

Be careful to obfuscate every secrets (credentials, token, public IP, ...) that could be visible in the output before copy-pasting

Readiness probe failed: Waiting for elasticsearch cluster to become ready (request params: "wait_for_status=green&timeout=1s" ) Cluster is not yet ready (request params: "wait_for_status=green&timeout=1s" )

Any additional context:

See #638 for changes that broke it.

@davidishee
Copy link
Author

On further review, I think -k is being passed in correctly. My use-case is still failing, but due to some other reason.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant