diff options
| author | ming.tang <ming.tang@daocloud.io> | 2023-07-17 09:52:33 +0800 |
|---|---|---|
| committer | ming.tang <ming.tang@daocloud.io> | 2023-07-17 10:01:43 +0800 |
| commit | 3378113433367d30704a25023055b7ee3f1c8e91 (patch) | |
| tree | 61321b2f92d6320024030c669a315c6248074177 /docs/proposals | |
| parent | Merge pull request #4842 from arnoldberlin/patch-1 (diff) | |
| download | kubeedge-3378113433367d30704a25023055b7ee3f1c8e91.tar.gz | |
update doc
Signed-off-by: ming.tang <ming.tang@daocloud.io>
Diffstat (limited to 'docs/proposals')
| -rw-r--r-- | docs/proposals/node-group-management.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/proposals/node-group-management.md b/docs/proposals/node-group-management.md index a3985fbf8..038a2e749 100644 --- a/docs/proposals/node-group-management.md +++ b/docs/proposals/node-group-management.md @@ -377,18 +377,18 @@ spec: overriders: replicas: 2 imageOverriders: - - component: "registry" + - component: "Registry" operator: "replace" value: "hangzhou.registry.io" - name: beijing overriders: replicas: 3 imageOverriders: - - component: "registry" + - component: "Registry" operator: "replace" value: "beijing.registry.io" ``` -Then two deployments called `nginx-hangzhou` and `nginx-beijing` will be created for hangzhou nodegroup and beijing nodegroup with `replicas: 2` and `replicas: 3` respectively. Pods running in hangzhou nodegroup will use the image `hangzhou.registry.io/nginx:latest` and pods running in beijing nodegroup will use the image `beijing.resistry.io/nginx.latest`. +Then two deployments called `nginx-hangzhou` and `nginx-beijing` will be created for hangzhou nodegroup and beijing nodegroup with `replicas: 2` and `replicas: 3` respectively. Pods running in hangzhou nodegroup will use the image `hangzhou.registry.io/nginx:latest` and pods running in beijing nodegroup will use the image `beijing.resistry.io/nginx:latest`. The service in the EdgeApplication will also be created and injected with label `groupmanagement.kubeedge.io/edgeapplication-name: nginx-app`. The endpointslice filter in the cloudcore will check the relative EdgeApplication when sending the endpointslice to the edgecore in some nodegroup. It will filter out endpoints not in that nodegroup. Then, clients running in hangzhou node group can only reach the 2 pod instances that are also running in hangzhou node group. The situation of beijing node group is the same. |