sayeedhussain opened a new issue, #6957: URL: https://github.com/apache/incubator-devlake/issues/6957
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) and found no similar issues. ### What happened We have deployed devlake using helm chart in AWS EKS cluster. We noticed that when basicAuth is enabled in config-ui, the /health endpoint which seems to be added as part of this PR https://github.com/apache/incubator-devlake/pull/5745 is not accessible without auth. Hitting /health shows up the authentication popup. Refer screenshot. <img width="1728" alt="Screenshot 2024-02-15 at 12 24 02 PM" src="https://github.com/apache/incubator-devlake/assets/1550131/a5e9dacb-b526-4052-81cb-4b0b84fe544e";> So we are not able to configure /health for our liveness/readiness probe. With basicAuth enabled, the existing probes also fail due to authencation error and the pods don't come up. To overcome this and for the config-ui pod to start, we had to disable the probes using kubectl patch deployment command. ### What do you expect to happen /health endpoint should be accessible without auth. ### How to reproduce 1. Deploy devlake through helm chart with basicAuth enabled. 2. Hit the /health endpoint. Basic auth pop-up will come up. ### Anything else Always reproducible. ### Version 0.21.0-beta1 ### Are you willing to submit PR? - [X] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
