opensearch-project / opensearch-project/data-prepper

[BUG] readinessProbe and livenessProbe fails when enable the

Open
#5,723 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Java
Stars
374
Forks
354
Avg merge
3d 18h
Merged PRs (30d)
8

Description

Describe the bug
A clear and concise description of what the bug is.

when enabling the authentication in data-prepper-config.yaml, the readinessProbe and livenessProbe fails with 401 error

config:
  data-prepper-config.yaml: |
    ssl: false
    serverPort: 4900
      authentication:
        http_basic:
          username: "data-prepper"
          password: "mys3cr3t"

To Reproduce
see above

Expected behavior
A clear and concise description of what you expected to happen.
In HELM, the data-prepper container's readinessProbe and livenessProbe shall consider when http_basic authentication is enabled in configuration.

Screenshots
If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

  • OS: [e.g. Ubuntu 20.04 LTS]
  • Version [e.g. 22]. HELM VERSION version: 0.3.1

Additional context
Add any other context about the problem here.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Helm chart's readinessProbe and livenessProbe configuration and the data-prepper-config.yaml authentication settings shown in the issue. Reproduce the deployment with http_basic authentication enabled and inspect why both probes receive 401 responses. Done means the probes succeed when authentication is enabled in the Helm deployment.

Written by the indexing model from the issue text.

Assessment

Tech stack
helm, kubernetes
Domain
devops, infrastructure
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.