[zh-cn] Sync extended-resource-node.md

Zhuzhenghao · Zhuzhenghao · commit 6c68cbbdc70c · 2023-01-30T16:30:48.000+08:00
diff --git a/content/zh-cn/docs/tasks/administer-cluster/extended-resource-node.md b/content/zh-cn/docs/tasks/administer-cluster/extended-resource-node.md
@@ -1,10 +1,12 @@
 ---
 title: &#20026;&#33410;&#28857;&#21457;&#24067;&#25193;&#23637;&#36164;&#28304;
 content_type: task
+weight: 70
 ---
 <!--
 title: Advertise Extended Resources for a Node
 content_type: task
+weight: 70
 -->
 
 <!-- overview -->
@@ -26,14 +28,16 @@ resources that would otherwise be unknown to Kubernetes.
 <!--
 ## Get the names of your Nodes
 
-Choose one of your Nodes to use for this exercise.
 -->
 ## &#33719;&#21462;&#20320;&#30340;&#33410;&#28857;&#21517;&#31216;
 
 ```shell
 kubectl get nodes
 ```
 
+<!--
+Choose one of your Nodes to use for this exercise.
+-->
 &#36873;&#25321;&#19968;&#20010;&#33410;&#28857;&#29992;&#20110;&#27492;&#32451;&#20064;&#12290;
 
 <!--
@@ -50,7 +54,7 @@ for your Node.
 &#20363;&#22914;&#65306;&#20551;&#35774;&#20320;&#30340;&#19968;&#20010;&#33410;&#28857;&#19978;&#24102;&#26377;&#22235;&#20010; dongle &#36164;&#28304;&#12290;
 &#19979;&#38754;&#26159;&#19968;&#20010; PATCH &#35831;&#27714;&#30340;&#31034;&#20363;&#65292;&#35813;&#35831;&#27714;&#20026;&#20320;&#30340;&#33410;&#28857;&#21457;&#24067;&#22235;&#20010; dongle &#36164;&#28304;&#12290;
 
-```shell
+```
 PATCH /api/v1/nodes/<your-node-name>/status HTTP/1.1
 Accept: application/json
 Content-Type: application/json-patch+json
@@ -95,13 +99,13 @@ curl --header "Content-Type: application/json-patch+json" \
   http://localhost:8001/api/v1/nodes/<your-node-name>/status
 ```
 
+{{< note >}}
 <!--
 In the preceding request, `~1` is the encoding for the character / in
 the patch path. The operation path value in JSON-Patch is interpreted as a
 JSON-Pointer. For more details, see
 [IETF RFC 6901](https://tools.ietf.org/html/rfc6901), section 3.
 -->
-{{< note >}}
 &#22312;&#21069;&#38754;&#30340;&#35831;&#27714;&#20013;&#65292;`~1` &#20026; patch &#36335;&#24452;&#20013; &ldquo;/&rdquo; &#31526;&#21495;&#30340;&#32534;&#30721;&#12290;
 JSON-Patch &#20013;&#30340;&#25805;&#20316;&#36335;&#24452;&#20540;&#34987;&#35299;&#26512;&#20026; JSON &#25351;&#38024;&#12290;
 &#26356;&#22810;&#32454;&#33410;&#65292;&#35831;&#26597;&#30475; [IETF RFC 6901](https://tools.ietf.org/html/rfc6901) &#30340;&#31532; 3 &#33410;&#12290;
@@ -119,21 +123,25 @@ The output shows that the Node has a capacity of 4 dongles:
   "example.com/dongle": "4",
 ```
 
-<!-- Describe your Node: -->
+<!--
+Describe your Node:
+-->
 &#25551;&#36848;&#20320;&#30340;&#33410;&#28857;&#65306;
 
-```shell
+```
 kubectl describe node <your-node-name>
 ```
 
-<!-- Once again, the output shows the dongle resource: -->
+<!--
+Once again, the output shows the dongle resource:
+-->
 &#36755;&#20986;&#20877;&#27425;&#23637;&#31034;&#20102; dongle &#36164;&#28304;&#65306;
 
 ```yaml
 Capacity:
- cpu:  2
- memory:  2049008Ki
- example.com/dongle:  4
+  cpu: 2
+  memory: 2049008Ki
+  example.com/dongle: 4
 ```
 
 <!--
@@ -260,9 +268,9 @@ Replace `<your-node-name>` with the name of your Node:
 
 ```shell
 curl --header "Content-Type: application/json-patch+json" \
---request PATCH \
---data '[{"op": "remove", "path": "/status/capacity/example.com~1dongle"}]' \
-http://localhost:8001/api/v1/nodes/<your-node-name>/status
+  --request PATCH \
+  --data '[{"op": "remove", "path": "/status/capacity/example.com~1dongle"}]' \
+  http://localhost:8001/api/v1/nodes/<your-node-name>/status
 ```
 
 <!--
@@ -275,29 +283,27 @@ kubectl describe node <your-node-name> | grep dongle
 ```
 
 <!--
-(you should not see any output)  
+(you should not see any output)
 -->
 (&#20320;&#24212;&#35813;&#30475;&#19981;&#21040;&#20219;&#20309;&#36755;&#20986;)
 
-
 ## {{% heading "whatsnext" %}}
 
 <!--
 ### For application developers
 
-* [Assign Extended Resources to a Container](/docs/tasks/configure-pod-container/extended-resource/)
+- [Assign Extended Resources to a Container](/docs/tasks/configure-pod-container/extended-resource/)
 
 ### For cluster administrators
 
-* [Configure Minimum and Maximum Memory Constraints for a Namespace](/docs/tasks/administer-cluster/memory-constraint-namespace/)
-* [Configure Minimum and Maximum CPU Constraints for a Namespace](/docs/tasks/administer-cluster/cpu-constraint-namespace/)
+- [Configure Minimum and Maximum Memory Constraints for a Namespace](/docs/tasks/administer-cluster/manage-resources/memory-constraint-namespace/)
+- [Configure Minimum and Maximum CPU Constraints for a Namespace](/docs/tasks/administer-cluster/manage-resources/cpu-constraint-namespace/)
 -->
 ### &#38024;&#23545;&#24212;&#29992;&#24320;&#21457;&#20154;&#21592;
 
-* [&#23558;&#25193;&#23637;&#36164;&#28304;&#20998;&#37197;&#32473;&#23481;&#22120;](/zh-cn/docs/tasks/configure-pod-container/extended-resource/)
-  
-### &#38024;&#23545;&#38598;&#32676;&#31649;&#29702;&#21592;
+- [&#23558;&#25193;&#23637;&#36164;&#28304;&#20998;&#37197;&#32473;&#23481;&#22120;](/zh-cn/docs/tasks/configure-pod-container/extended-resource/)
 
-* [&#20026;&#21517;&#23383;&#31354;&#38388;&#37197;&#32622;&#26368;&#23567;&#21644;&#26368;&#22823;&#20869;&#23384;&#32422;&#26463;](/zh-cn/docs/tasks/administer-cluster/manage-resources/memory-constraint-namespace/)
-* [&#20026;&#21517;&#23383;&#31354;&#38388;&#37197;&#32622;&#26368;&#23567;&#21644;&#26368;&#22823; CPU &#32422;&#26463;](/zh-cn/docs/tasks/administer-cluster/manage-resources/cpu-constraint-namespace/)
+### &#38024;&#23545;&#38598;&#32676;&#31649;&#29702;&#21592;
 
+- [&#20026;&#21517;&#23383;&#31354;&#38388;&#37197;&#32622;&#26368;&#23567;&#21644;&#26368;&#22823;&#20869;&#23384;&#32422;&#26463;](/zh-cn/docs/tasks/administer-cluster/manage-resources/memory-constraint-namespace/)
+- [&#20026;&#21517;&#23383;&#31354;&#38388;&#37197;&#32622;&#26368;&#23567;&#21644;&#26368;&#22823; CPU &#32422;&#26463;](/zh-cn/docs/tasks/administer-cluster/manage-resources/cpu-constraint-namespace/)
