Disable authentication for Management API

Proposal

Hi,

I setup basic auth (using --web.config.file), when I deploy my image of alertmanager on Kubernetes, probes (startup, readiness) are not able to check the Management API because they are not providing authentication header (HTTP 401).
As a consequence the pod is not healthy.

Could it be possible to disable authentication for Management API ?

From our in-house Kubernetes expert:
Probe definitions are part of the static Pod specification and are validated before the container starts. Vault secrets are injected only at runtime, which means probes cannot consume Vault secrets, environment variables, or templated values (Helm, ArgoCD, etc.) for authentication headers.
The recommended and Kubernetes-approved approach is to keep health endpoints unauthenticated. Health checks should be lightweight, fast, and dependency-free.

As an example, such feature is implemented in InfluxDb by specifying a startup parameter "--disable-authz health" which disabled in this example the "health" api.

Thanks.

Start by tracing authentication for the Management API and the --web.config.file path, then identify how startup and readiness probes reach those endpoints. Clarify which health endpoints must remain unauthenticated and verify that the resulting behavior keeps the pod healthy without weakening authentication for other Management API operations.