[Improvement-12563]Add authentication to the Prometheus endpoint and adapt it for Kubernetes (K8S) environments.

[njnu-seafish]

Purpose of the pull request

close #12563

Brief change log

Add authentication to the Prometheus endpoint and adapt it for Kubernetes (K8S) environments.

This pull request is already covered by existing tests, such as (please describe tests).

--api
curl -s 'http://127.0.0.1:12345/dolphinscheduler/actuator/prometheus' -H 'Authorization: Basic xxxxx'
--alert
curl -s 'http://127.0.0.1:50053/actuator/prometheus' -H 'Authorization: Basic xxxxx'
--master
curl -s 'http://127.0.0.1:5679/actuator/prometheus' -H 'Authorization: Basic xxxxx'
--worker
curl -s 'http://127.0.0.1:1235/actuator/prometheus' -H 'Authorization: Basic xxxxx'

Pull Request Notice

Pull Request Notice

If your pull request contains incompatible change, you should also add it to docs/docs/en/guide/upgrade/incompatible.md

[ruanwenjun]

Why don't directly use the security feature provided by springboot

management:
  security:
    enabled: true

[njnu-seafish]

Why don't directly use the security feature provided by springboot

management:
  security:
    enabled: true

First, it didn't take effect, possibly due to issues with my testing.
Secondly, using custom logic facilitates the unification of the four services and can also be adapted to service health checks in Kubernetes (K8S) environments.

[ruanwenjun]

Why don't directly use the security feature provided by springboot

management:
  security:
    enabled: true

First, it didn't take effect, possibly due to issues with my testing. Secondly, using custom logic facilitates the unification of the four services and can also be adapted to service health checks in Kubernetes (K8S) environments.

It didn't take effect, might due to we should add Spring Security module, and we can filter the health endpoint in security check.

[njnu-seafish]

Why don't directly use the security feature provided by springboot

management:
  security:
    enabled: true

First, it didn't take effect, possibly due to issues with my testing. Secondly, using custom logic facilitates the unification of the four services and can also be adapted to service health checks in Kubernetes (K8S) environments.

It didn't take effect, might due to we should add Spring Security module, and we can filter the health endpoint in security check.

Why don't directly use the security feature provided by springboot

management:
  security:
    enabled: true

First, it didn't take effect, possibly due to issues with my testing. Secondly, using custom logic facilitates the unification of the four services and can also be adapted to service health checks in Kubernetes (K8S) environments.

It didn't take effect, might due to we should add Spring Security module, and we can filter the health endpoint in security check.

Alright, I will spend some time to test it.

[njnu-seafish]

@ruanwenjun @SbloodyS Could u plz help review when available? Thanks.

[sonarqubecloud]

Quality Gate failed

Failed conditions
0.0% Coverage on New Code (required ≥ 60%)

See analysis details on SonarQube Cloud