ATTU Ingress path is hard-coded to "/"

[VincentDu2021]

Checking "https://github.com/milvus-io/milvus-helm/blob/master/charts/milvus/templates/attu-ingress.yaml#L42", does this mean currently ATTU is only meant to be used in a milvus cluster? In our case, we deploy milvus into a namespace and want to consider ATTU as one of the service, so using "/" as the endpoint path is not viable for us.

While we can work around by editing the "path" of the ingress object in the cluster to make the service available, the rest of the API calls wouldn't work, such as:
https://xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.amazonaws.com/api/v1/milvus/connect

Any idea if this can be supported?