Admin relies on registry, config center as original data sources, so it needs to know the addresses to connect to them. Currently, admin reads admin.yml for those addresses, but the addresses are set to something like 127.0.0.1:2181 when the image is built, which are not real addresses.

We need to have a way to pass the right Zookeeper or Nacos addresses into admin. The right time to do this I think is when these components are installed, so by the time admin is started it already knows the right zookeeper/nacos addresses (typically zookeeper.dubbo-system.svc).

现状：

dubboctl create -l java //当前目录必须为空，即要求用户提前创建空目录

期望：

• 能否支持直接新建子目录，所有生成的资源放子目录
• dubboctl create -l java dubbo-demo

Improve the Admin console and fix its bugs.Verify zk and nacos as registration center

description

元数据的获取是关键，未来以triple/http为主

• 仅支持指定单台机器（机器暴露接口，支持先读取metadata，proto或语言特有）
• 可参考 connect、grpc-awesome 等那边的测试交互。
• 老的测试能力只针对 dubbo java，继续增强保留

components

• backend
• frontend

depends on

#78

The usage should only be printed when the user pass the wrong flags (or some required flags are not set). But dubboctl would also print usage strings when a command failed to execute.

Reproduction steps

# under the go template workspace
export DOCKER_HOST="unix:///path/to/no/exist.sock"
dubboctl build --image test:latest -d

The command would fail and print usage:

As the flags is correct in this case, the program should only print the actual error, rather than also print the usages.

description

做成一个个的圆盘，把页面填上就行了（集群直观数据、简单点的）

• 应用数、机器数、服务数、数据面版本分布
• 底部也可以加一些文档链接

components

• backend
• frontend

depends on

#78

Supporting night mode can enhance the user experience. Consider implementing it.

It should be 'dubboctl deploy --output=deployment.yml', but not '--out'

Generate kube.yaml, then try to push image to remote. This will guarantee at least the yaml file can be generated on push failure scenarios.

在API：段落，servie是错误的，正确是：service

dubbojava's dubbo-cp data plane adaptation。You can refer to
apache/dubbo#11928
test/testclient/ddsc.go(The specific rules can be seen inside)
For certificate related information, please refer to the PR above or consult 远云

当前dubbo已经对接过xds了，也就是以Istio作为网格控制面，然后dubbo兼容了Istio的一些规则。那么当前的dubbo对接dubbo-cp道理其实是类似的，我们的协议叫做dds，这是由xds这个名字改编而来的。它的作用是与Istio网格控制面互相配合，完成具有dubbo特色的服务治理(例如dubbo流量管控)

工作流程图：

具体的工作流程：

• 当dubbo服务启动的时候需要把接口-应用的映射关系发送给dubbo-cp。然后监听他动态的获取接口-应用映射的变化。
• 监听流量管控，authentication，authorization的规则，动态的获取配置并在数据面生效

以远云老师的pr为主进行参考，但是里面有一些东西有微弱的改变，例如数据的传输之前是json序列化，现在是protobuf序列化，请求的Type修改成了GVK等等具体看test/testclient/ddsc.go，以及里面的规则定义。

这就是主要的流程了！

但是除了这个之外，有一些证书的机制需要进行添加。证书的机制就主要是参考远云老师的pr了。

具体流程图如下：

这其中的过程可能比较复杂，需要详细的参考远云老师的pr。

• 控制面：实现了一个CA复杂为网格中的各个服务签发证书，并将证书颁发给各个服务，具体的做法是通过动态准入控制器的方式挂载到Pod里面去了，同时添加了环境变量，只需要读取环境变量就可以获取路径了。
• 数据面：在网格中服务相互之前发起TCP通信的时候，dubbo sdk会拦截服务请求，采用证书进行双向TLS认证并建立一个TLS连接，使用改TLS连接来在网格中传输数据。

具体的参考远云老师的pr。

规则，协议参考test/testclient/ddsc.go即可，和pr差别没有很大。

dds协议最重要的就是推送机制，目前需要对其进行优化，pkg/dds。

After the new version of the application stabilizes, the plan is to replace the Traefik Ingress controller with the community-native Ingress controller.

Reasons for the change:

1. Seamless integration with the Kubernetes core API ecosystem.
2. Dependency decoupling, reducing reliance on plugins, middleware, and extension mechanisms.
3. Adherence to standardization, providing improved compatibility and stability.

We should define an caching or adapting layer for dubbo-cp console to work with both Universal and Kubernetes mode, it should be able to:

1. Hide the implementation details of Zookeeper/Nacos or Kubernetes server.
2. Provide unified API for different dubbo-cp console features.

Reference implementations we have now:

1. Dubbo-cp, Universal cache implementation in https://github.com/apache/dubbo-kubernetes/tree/master/pkg/admin/cache
2. Kiali, Kubernetes/Mesh cache implementation in https://github.com/kiali/kiali/tree/master/kubernetes
3. Kuma, the Universal and Kubernetess mode in https://github.com/kumahq/kuma

I didn't run dubboctl manifest install before running dubboctl deploy. Is that the reason which caused this?

description

已经做了一部分了，增加预览、受影响ip等易用性提升

• 场景分类
• 增加 preview 步骤，然后创建，以crd为载体
• Affected Workloads（pod/ip）
• Yaml Preview（universl/kubernetes）

components

• backend
• frontend

depends on

#78

The template dockerfile content is now placed in a go source file. Consider extracting the template dockerfile content into separate dockerfiles, like go.dockerfile, java.dockerfile, and using go:embed to embed dockerfile content as string variables in a index go source file.

By this way, we could get dockerfile highlighting feature provided by IDE and it will be easier to use tools to check the syntax and format the source file. It also makes it easier for us to support more runtimes, modify individual runtime configuration files, etc.

目前dubbo-control plane有一个代码生成工具，改工具的目的是为了开发者快速的添加crd资源。但是这个生成工具做的不够好，需要进行改善。任务需要对该工具提出自己改善的提案，然后参与工具整体的改进。在tools目录下。具体的可以参考kuma和istio相关的代码生成工具。

At present, dubboctl and dubbo-kubernetes control plane need detailed testing. I need a classmate to assist me in testing together.

Hi，我直接使用jar生成了docker文件，并尝试在kubernetes上部署，但是provider显示以下日志：

Error: Could not find or load main class com.alibaba.dubbo.demo.consumer.Provider
Error: Could not find or load main class com.alibaba.dubbo.demo.consumer.Provider

请帮忙看看

• I have searched the issues of this repository and believe that this is not a duplicate.
• I have checked the REAMDE of this repository and believe that this is not a duplicate.

Environment

• dubbo-admin-ui: 0.3.0-SNAPSHOT

Steps to reproduce this issue

1. upgrade vue2.6 to ^3.3.4
2. use ui with antdv ^4.0.7

Expected Result

The Vue 3 framework offers improved performance compared to Vue 2.6, resulting in higher efficiency for our UI project.

Actual Result

我想试用 dubbo、kubernetes 相关功能，发现所有的 sample 都引用了 dubbo-registry-kubernetes 这个包，但该包在 dubbo 的主页上没有任何打包记录。在任何 sample 中都没有提到 dubbo-registry-kubernetes 项目，但是所有人都用到了，缺了该项目根本就起不来。

版本不一致
每个 sample 的版本也不尽一致，有的是 3.0.1-SNAPHOT，有的是 3.0.2 。

在 https://mvnrepository.com/artifact/org.apache.dubbo/dubbo-registry-kubernetes 上，这个包已经到 3.0.5 了，怎么打包上去的？为什么在本项目看不到 Release 记录？如果这个包是本项目的话，为什么没有代码提交记录？

我们需要让dubboctl的build镜像能力支持podman，目前仅支持docker。

Error: cannot create docker client: docker API not available

Environment

MacBook 
Apple M1 Pro

Client:
 Cloud integration: v1.0.35-desktop+001
 Version:           24.0.5
 API version:       1.43
 Go version:        go1.20.6
 Git commit:        ced0996
 Built:             Fri Jul 21 20:32:30 2023
 OS/Arch:           darwin/arm64
 Context:           desktop-linux

Server: Docker Desktop 4.22.1 (118664)
 Engine:
  Version:          24.0.5
  API version:      1.43 (minimum version 1.12)
  Go version:       go1.20.6
  Git commit:       a61e2b4
  Built:            Fri Jul 21 20:35:38 2023
  OS/Arch:          linux/arm64
  Experimental:     false
 containerd:
  Version:          1.6.21
  GitCommit:        3dce8eb055cbb6872793272b4f20ed16117344f8
 runc:
  Version:          1.1.7
  GitCommit:        v1.1.7-0-g860f061
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

Customize a builder so that users can quickly pull it in China and cater to dubbo's unique needs so that the program can run after it is built.

1. Kubernetes: Update to the latest template.
2. Charts: Remove Nacos registry.
3. Naming convention adjustment.
4. File Redundancy Optimization.
5. Other

We need to add k8s-related data to the observability of dubbo-kubernetes. For details, please refer to https://github.com/kiali/kiali.
Code contribution is under pkg/admin (specific details can be discussed at that time)

description

登陆与认证鉴权能力，kubernetes 实现参考 Kiali/kubedashboard 等

components

• backend
• frontend

depends on

#78

A sub-feature of #80

We already have equivalent metrics support for https://istio.io/latest/docs/reference/config/metrics/ in our dubbo-java and dubbo-go SDK. So we can reference Kiali's graph implementation to draw our own graghs.

• I have searched the issues of this repository and believe that this is not a duplicate.
• I have checked the REAMDE of this repository and believe that this is not a duplicate.

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

Incorporate KEDA and HPA support into the project's charts to enhance the project's automatic scaling capabilities. This will help better manage container scaling, automatically adjusting the number of containers based on load requirements.

Why is this Feature Needed

1. Enhanced Automatic Scaling Support

   • KEDA automatically scales applications based on event sources such as queues and message queues.
   • HPA automatically scales based on CPU and memory usage.

2. Facilitate Ease of Use for Users. Users will find it easier to integrate these automatic scaling features with the project.

3. KEDA and HPA are widely adopted in the Kubernetes community. By adding this support, it enhances the project's appeal.

Contribute Feature

I am willing to contribute to this feature. I have experience using KEDA and HPA in Kubernetes environments and am familiar with the project's chart structure. My planned initial steps include:

• Research the current project's chart structure and dependencies.
• Add configuration options for KEDA and HPA to the charts, making it easy for users to enable these features.
• Update documentation to reflect the usage of these new features.

Additional context

If there is any additional information or supplementary content, I would be happy to hear and consider it. I hope this feature will bring greater value to the project and the community.

该项目中使用到了gogo proto，但该项目在前几个月停止维护了，因此需要将其替换，这可能会涉及到control plane小范围的重构。

description

监控控制面进程自身

• dubbo-cp 相关基础信息：连接的registry、kubernetes集群、工作模式、配置文件等
• 单独显示 dubbo-cp 进程的相关 metrics 指标

components

• backend
• frontend

depends on

#78

When dubboctl implements automatic injection of registration center configuration, it is unclear which one of k8s, zookeeper, and nacos the user is using.

Users need to be able to configure which registration center they need.

Improve dubbogo's internal kubernetes-related mechanism to align it with the life cycle of dubboctl deploy generated templates and so on...

description

围绕一个应用出发，展示应用的详细：

• 如果是k8s，就是 kubernetes service 详情
• deployment/pod/ip 详情
• 发布的服务详情
• 消费的服务详情
• 显示流量的聚合页面 (类似当前我们做的 Grafana 大盘)
• 从当前应用出发生成的应用拓扑/依赖关系

components

• backend
• frontend

depends on

#78

Would the following be better?

dubboctl deploy 
# deploy 读取dubbo.yml上下文，如果之前build过，则以上命令直接通过，push默认是true
# 如果没build过，则promot，提示输入 image tag，push默认是true

dubboctl deploy --image docker.io/testuser/testdubbo:latest
# 跳过build，直接根据指定image生成k8s yaml

description

单机/Workload/ip 详情：

• 这部分可以做的比较多，根据情况来，很多可以参考的，如kiali/springboot admin 等。

components

• backend
• frontend

depends on

#78

dubbogo's dubbo-cp data plane adaptation。You can refer to
apache/dubbo#11928
test/testclient/ddsc.go(The specific rules can be seen inside)
For certificate related information, please refer to the PR above or consult 远云

当前dubbo已经对接过xds了，也就是以Istio作为网格控制面，然后dubbo兼容了Istio的一些规则。那么当前的dubbo对接dubbo-cp道理其实是类似的，我们的协议叫做dds，这是由xds这个名字改编而来的。它的作用是与Istio网格控制面互相配合，完成具有dubbo特色的服务治理(例如dubbo流量管控)

工作流程图：
dubbo-cp

具体的工作流程：

当dubbo服务启动的时候需要把接口-应用的映射关系发送给dubbo-cp。然后监听他动态的获取接口-应用映射的变化。
监听流量管控，authentication，authorization的规则，动态的获取配置并在数据面生效
以远云老师的pr为主进行参考，但是里面有一些东西有微弱的改变，例如数据的传输之前是json序列化，现在是protobuf序列化，请求的Type修改成了GVK等等具体看test/testclient/ddsc.go，以及里面的规则定义。

这就是主要的流程了！

但是除了这个之外，有一些证书的机制需要进行添加。证书的机制就主要是参考远云老师的pr了。

具体流程图如下：

这其中的过程可能比较复杂，需要详细的参考远云老师的pr。

控制面：实现了一个CA复杂为网格中的各个服务签发证书，并将证书颁发给各个服务，具体的做法是通过动态准入控制器的方式挂载到Pod里面去了，同时添加了环境变量，只需要读取环境变量就可以获取路径了。
数据面：在网格中服务相互之前发起TCP通信的时候，dubbo sdk会拦截服务请求，采用证书进行双向TLS认证并建立一个TLS连接，使用改TLS连接来在网格中传输数据。
具体的参考远云老师的pr。

规则，协议参考test/testclient/ddsc.go即可，和pr差别没有很大。

Write some scripts for project release. For details, you can refer to Istio’s approach.

There is a problem with the path of index.html generated after the current-end UI is packaged, causing the resource to not be found.

.
├── dubbo-admin-info.json
├── dubbo.ico
├── echarts-en.min.js
├── fonts
│   ├── flUhRq6tzZclQEJ-Vdg-IuiaDsNcIhQ8tQ.woff2
│   ├── KFOlCnqEu92Fr1MmEU9fABc4AMP6lbBP.woff2
│   ├── KFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2
│   ├── KFOlCnqEu92Fr1MmEU9fBxc4AMP6lbBP.woff2
│   ├── KFOlCnqEu92Fr1MmEU9fCBc4AMP6lbBP.woff2
│   ├── KFOlCnqEu92Fr1MmEU9fChc4AMP6lbBP.woff2
│   ├── KFOlCnqEu92Fr1MmEU9fCRc4AMP6lbBP.woff2
│   ├── KFOlCnqEu92Fr1MmEU9fCxc4AMP6lbBP.woff2
│   ├── KFOlCnqEu92Fr1MmSU5fABc4AMP6lbBP.woff2
│   ├── KFOlCnqEu92Fr1MmSU5fBBc4AMP6lQ.woff2
│   ├── KFOlCnqEu92Fr1MmSU5fBxc4AMP6lbBP.woff2
│   ├── KFOlCnqEu92Fr1MmSU5fCBc4AMP6lbBP.woff2
│   ├── KFOlCnqEu92Fr1MmSU5fChc4AMP6lbBP.woff2
│   ├── KFOlCnqEu92Fr1MmSU5fCRc4AMP6lbBP.woff2
│   ├── KFOlCnqEu92Fr1MmSU5fCxc4AMP6lbBP.woff2
│   ├── KFOlCnqEu92Fr1MmWUlfABc4AMP6lbBP.woff2
│   ├── KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
│   ├── KFOlCnqEu92Fr1MmWUlfBxc4AMP6lbBP.woff2
│   ├── KFOlCnqEu92Fr1MmWUlfCBc4AMP6lbBP.woff2
│   ├── KFOlCnqEu92Fr1MmWUlfChc4AMP6lbBP.woff2
│   ├── KFOlCnqEu92Fr1MmWUlfCRc4AMP6lbBP.woff2
│   ├── KFOlCnqEu92Fr1MmWUlfCxc4AMP6lbBP.woff2
│   ├── KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
│   ├── KFOmCnqEu92Fr1Mu4WxKKTU1Kvnz.woff2
│   ├── KFOmCnqEu92Fr1Mu5mxKKTU1Kvnz.woff2
│   ├── KFOmCnqEu92Fr1Mu72xKKTU1Kvnz.woff2
│   ├── KFOmCnqEu92Fr1Mu7GxKKTU1Kvnz.woff2
│   ├── KFOmCnqEu92Fr1Mu7mxKKTU1Kvnz.woff2
│   └── KFOmCnqEu92Fr1Mu7WxKKTU1Kvnz.woff2
├── html
│   ├── 50x.html
│   ├── dubbo-admin-info.json
│   ├── dubbo.ico
│   ├── echarts-en.min.js
│   ├── fonts
│   │   ├── flUhRq6tzZclQEJ-Vdg-IuiaDsNcIhQ8tQ.woff2
│   │   ├── KFOlCnqEu92Fr1MmEU9fABc4AMP6lbBP.woff2
│   │   ├── KFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2
│   │   ├── KFOlCnqEu92Fr1MmEU9fBxc4AMP6lbBP.woff2
│   │   ├── KFOlCnqEu92Fr1MmEU9fCBc4AMP6lbBP.woff2
│   │   ├── KFOlCnqEu92Fr1MmEU9fChc4AMP6lbBP.woff2
│   │   ├── KFOlCnqEu92Fr1MmEU9fCRc4AMP6lbBP.woff2
│   │   ├── KFOlCnqEu92Fr1MmEU9fCxc4AMP6lbBP.woff2
│   │   ├── KFOlCnqEu92Fr1MmSU5fABc4AMP6lbBP.woff2
│   │   ├── KFOlCnqEu92Fr1MmSU5fBBc4AMP6lQ.woff2
│   │   ├── KFOlCnqEu92Fr1MmSU5fBxc4AMP6lbBP.woff2
│   │   ├── KFOlCnqEu92Fr1MmSU5fCBc4AMP6lbBP.woff2
│   │   ├── KFOlCnqEu92Fr1MmSU5fChc4AMP6lbBP.woff2
│   │   ├── KFOlCnqEu92Fr1MmSU5fCRc4AMP6lbBP.woff2
│   │   ├── KFOlCnqEu92Fr1MmSU5fCxc4AMP6lbBP.woff2
│   │   ├── KFOlCnqEu92Fr1MmWUlfABc4AMP6lbBP.woff2
│   │   ├── KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
│   │   ├── KFOlCnqEu92Fr1MmWUlfBxc4AMP6lbBP.woff2
│   │   ├── KFOlCnqEu92Fr1MmWUlfCBc4AMP6lbBP.woff2
│   │   ├── KFOlCnqEu92Fr1MmWUlfChc4AMP6lbBP.woff2
│   │   ├── KFOlCnqEu92Fr1MmWUlfCRc4AMP6lbBP.woff2
│   │   ├── KFOlCnqEu92Fr1MmWUlfCxc4AMP6lbBP.woff2
│   │   ├── KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
│   │   ├── KFOmCnqEu92Fr1Mu4WxKKTU1Kvnz.woff2
│   │   ├── KFOmCnqEu92Fr1Mu5mxKKTU1Kvnz.woff2
│   │   ├── KFOmCnqEu92Fr1Mu72xKKTU1Kvnz.woff2
│   │   ├── KFOmCnqEu92Fr1Mu7GxKKTU1Kvnz.woff2
│   │   ├── KFOmCnqEu92Fr1Mu7mxKKTU1Kvnz.woff2
│   │   └── KFOmCnqEu92Fr1Mu7WxKKTU1Kvnz.woff2
│   ├── index.html
│   ├── OpenSans.css
│   └── static
│   ├── css
│   │   ├── app.4ab00ae8.css
│   │   ├── app.888953a3.css
│   │   ├── app.f8af26eb.css
│   │   ├── chunk-vendors.15048f58.css
│   │   ├── chunk-vendors.90cf4675.css
│   │   └── chunk-vendors.ad39ed5a.css
│   ├── img
│   │   ├── jsoneditor-icons.94cc3007.svg
│   │   └── max_btn.546521f3.svg
│   └── js
│   ├── app.13889972.js
│   ├── app.13889972.js.map
│   ├── braceBase.26ea46f8.js
│   ├── braceBase.26ea46f8.js.map
│   ├── chunk-vendors.6ea1db8a.js
│   └── chunk-vendors.6ea1db8a.js.map
├── index.html
├── OpenSans.css
└── static
├── css
│   ├── app.4ab00ae8.css
│   └── chunk-vendors.90cf4675.css
├── img
│   ├── jsoneditor-icons.94cc3007.svg
│   └── max_btn.546521f3.svg
└── js
├── app.13889972.js
├── app.13889972.js.map
├── braceBase.26ea46f8.js
├── braceBase.26ea46f8.js.map
├── chunk-vendors.6ea1db8a.js
└── chunk-vendors.6ea1db8a.js.map

Steps to reproduce this issue

1. git clone https://github.com/apache/dubbo-kubernetes.git
2. cd app/dubboctl
3. go build -o dubboctl main.go
4. mv ./dubboctl ~/Downloads
5. rm -f -R dubbo-kubernetes （project directory）
6. ~/Downloads/dubboctl profile list

Error: open /Users/jun/java/dubbo/dubbo-kubernetes/deploy/profiles: no such file or directory

7. app/dubboctl/identifier/env.go

var (
	_, b, _, _ = runtime.Caller(0)
	// Root folder of dubbo-admin
	// This relies on the fact this file is 3 levels up from the root; if this changes, adjust the path below
	Root            = filepath.Join(filepath.Dir(b), "../../..")
	Deploy          = filepath.Join(Root, "/deploy")
	Charts          = filepath.Join(Deploy, "/charts")
	Profiles        = filepath.Join(Deploy, "profiles")
	Addons          = filepath.Join(Deploy, "addons")
	AddonDashboards = filepath.Join(Addons, "dashboards")
	AddonManifests  = filepath.Join(Addons, "manifests")
)

The Root value is project source code directory when is build, so dubboctl can not run standalone.

link: https://github.com/apache/dubbo-kubernetes/blob/master/README.md

• I have searched the issues of this repository and believe that this is not a duplicate.
• I have checked the REAMDE of this repository and believe that this is not a duplicate.

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

Incorporate charts distributed storage system capabilities. Integrate the Rook distributed storage solution into the cluster to provide persistent storage support for containerized applications.

Why is this Feature Needed

Storage Management: Managing distributed storage systems is typically a complex task, involving node management, data distribution, backups, and fault handling, among others, which can be simplified.

Compliance with CSI Standard: The standard Container Storage Interface (CSI) enables containerized applications to seamlessly access and manage storage without needing to understand the underlying details of the storage system.

Data Persistence: Data can be retained even if containers are restarted or migrated.

Across Clouds and Hybrid Cloud: Deploying or migrating containerized applications between different cloud providers, making it well-suited for organizations with multi-cloud strategies or hybrid cloud deployment requirements.

RBD

rbd:
      monitors:
      - 10.100.51.74:6789
      pool: rook-rbd
      image: demo
      fsType: ext4
      user: csi-rbd-node
      secretRef:
        name: ceph-secret

CephFS

cephfs:
      monitors:
      - 10.100.51.74:6789
      path: /
      user: csi-cephfs-node
      secretRef:
        name: ceph-secret

S3

gateway:
    sslCertificateRef:
    port: 80
    instances: 2

SNAPSHOT

source:
    persistentVolumeClaimName:  <rbd-pvc>  # cephfs-pvc

Contribute Feature

I have experience using Rook in a large-scale production environment, enabling users to deploy and manage distributed storage systems more easily. Through Rook integration, I aim to provide users with a comprehensive containerized storage solution to meet the needs of their applications.

Additional context

If there is any additional information or supplementary content, I would be happy to hear and consider it. I hope this feature will bring greater value to the project and the community.

这个坑挖得，连很多基本的功能都跑不通，就放上来了，也不维护，直接删repository不行吗？

We should consider installing an ingress and ingress controller for easier access to applications and components from outside of the cluster.

description

就是一个表格，如展示以下内容：

名称、命名空间、label(特定labal)、发布服务数、订阅服务数

components

• backend
• frontend

depends on

#78

当前dubboctl会根据用户install了哪些组件自动将相应的注册中心的地址注入到k8s的yaml文件，不过目前的注入是在使用dubboctl deploy生成的yaml的情况下的。当前需要给用户提供一个选择，也就是不使用dubboctl deploy生成的yaml文件，用户自己写的yaml文件也可以去动态的注入。
具体的做法是在dubboctl install的阶段将动态准入控制器安装到k8s apiserver，然后在dubbo-injection=enabled的命名空间中的应用实现注入，在打了"dubbo-deploy"="enabled"的命名空间中去查找zk或者nacos的Pod里面有没有打上自动注入的labels（"dubbo.apache.org/zookeeper"="true"，"dubbo.apache.org/nacos"="true"），如果同时有的话zk优先，用动态注入控制器为用户自己撰写的yaml文件添加DUBBO_REGISTRY_ADDRESS地址，格式为 zookeeper://zookeeper.dubbo-system.svc类似这样。