dns

Backgroud

背景

There are three ways of getting arguments in the client module now, from the properties、from the Jvm arguments and from the system environment. so it needs an unified way that get arguments.

现在总共有3种获取参数的方式在客户端模块中, 有从 properties中获取的、从Jvm参数获取的和从System环境变了中获取的. 所以需要一种统一获取参数的方式.

The reasons are as follows:

• switch arguments getting order
• better mock test

原因如

What would you like to be added:
Currently there is the option to configure a --annotation-filter and a --source filter [0]. Since Kubernetes 1.19 the Ingress Resource was promoted to GA and got a new ingressClassName field.

I'd like to have a opti

Is your feature request related to a problem? Please describe.

When doing things such as migrating it is important to know the architecture of processes. ps doesn't currently list the architecture of processes.

Describe the solution you'd like

ps should list architecture of each process

Describe alternatives you've considered

None :(

Is your feature request related to a problem? Please describe.

Similar to how Bitcoin has a prune=1 option that removes old blocks, Stacks should have this too to save storage space on nodes.

Describe the solution you'd like

An option in the config to prune chaindata via RPC or limiting it to a certain number of MiB

Describe alternatives you've considered

None