Howard Lau

装一下 `noto-sans-cjk` 这个字体包就好了

Although we have `kustomize` deployment templates, I think Helm is more common

AFAIK, multiplexing HTTP and gRPC is possible. But I don't know if an ingress controller supports this. Maybe need refactoring on filer. Maybe a reverse proxy will work?

Seems it is impossible to open more than one ports on the exact same ingress path. So I think multiplexing is the only way. Have you tried `grpc-gateway`? `etcd` uses...

> grpc-gateway needs to start with a grpc implementation and then generate REST APIs. > > How about adding another ingress for the filer grpc port? I think that still...

> grpc-gateway needs to start with a grpc implementation and then generate REST APIs. > > How about adding another ingress for the filer grpc port? I think grpc-gateway also...

That will work. But may not seamlessly integrate with users' own ingress controller. I prefer two-path method, i.e. one path for http and another for grpc

that's quite easy. we can just query information from the masters and update any fields we like to the object.

@chrislusf I wonder if there is a more programmatic way to execute commands. Otherwise we have to parse the plain text output of the shell.

> For example, in the operator code, we can invoke this function directly, https://github.com/chrislusf/seaweedfs/blob/master/weed/shell/command_volume_balance.go#L63 > > We can refactor the command execution code to use typed error. It seems that...