github-actions[bot] commented on issue #9486: URL: https://github.com/apache/dolphinscheduler/issues/9486#issuecomment-1098630282
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement. ### Description I have a DolphinScheduler instance on Azure K8S cluster. The DolphinScheduler's API service is exposed to public network through by nginx ingress. To allow certain IP ranges to access DolphinScheduler, nginx ingress white list is configured, for instance: ````text ingress: enabled: true path: "/dolphinscheduler" annotations: nginx.ingress.kubernetes.io/whitelist-source-range: 10.0.0.0/14 ```` I'd like to contribute this to the community. Chinese Version: We use nginx-ingress to expose the DolphinScheduler API service deployed by the Azure K8S cluster to the public network, which is convenient for viewing, operating and maintaining DolphinScheduler. However, public network access brings security risks, so the IP whitelist function of nginx-ingress is used to limit it. example: ````text ingress: enabled: true path: "/dolphinscheduler" annotations: nginx.ingress.kubernetes.io/whitelist-source-range: 10.0.0.0/14 ```` We would like to contribute to the DolphinScheduler community ### Use case In K8S, setup dolphinscheduler ingress IP whitelist and enhance security . **Chinese** In k8S cluster, you can set IP whitelist for DolphinScheduler Ingress ### Related issues _No response_ ### Are you willing to submit a 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]
