Authentication required for Kubernetes liveness endpoint?


why does /api/v2/system/liveness require authentication? No data l(except of the status code 200) is “exposed” and the same information may be retrieved by just navigating to the UI start page which by showing the login mask already somehow states, that Sonarqube is alive.

Best Regards

Hey Mirko

Instead of restarting the discussion here, I would encourage you to follow-up on your existing thread (since there was already a lot of good discussion there)

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.