kaijli-bigdata opened a new issue, #17144: URL: https://github.com/apache/dolphinscheduler/issues/17144
### Search before asking - [x] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues. ### What happened In DolphinScheduler version 3.2.2, the alertServer service registers its address in Zookeeper using the Pod name (e.g., alert-server-7d6f7b8d8f-zc4h9) instead of a stable or resolvable address. In a Kubernetes environment, this leads to alert failure, because other components are unable to resolve the Pod name across the cluster or outside the namespace. As a result, alerts are not delivered properly.    ### What you expected to happen The host registered in Zookeeper can be either the alertServer service name or the service IP. This way, the api can call the alertServer service. ### How to reproduce Deploy DolphinScheduler 3.2.2 in a Kubernetes environment. Make sure that the alertServer is configured and running as part of the deployment. Verify that the alertServer registers its address in Zookeeper using the Pod name (e.g., alert-server-7d6f7b8d8f-zc4h9). Check the Zookeeper service to verify that it contains the Pod name as the registered address. Try to call the alert server from another service in the cluster using the registered address. Observe the failure in the alert server connection due to the Pod name not being resolvable by other services. ### Anything else _No response_ ### Version 3.2.x ### 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]
