Add admonition type to shortcode (#9482)

* Change existing admon blocks

* Fix includes issue

content/zh/docs/tasks/access-application-cluster/create-external-load-balancer.md

@@ -152,7 +152,7 @@ IP 地址列在 `LoadBalancer Ingress` 旁边。
 
 {{< note >}}
 <!--
-**Note**: If you are running your service on Minikube, you can find the assigned IP address and port with:
+If you are running your service on Minikube, you can find the assigned IP address and port with:
 -->
 **注意：** 如果您在 Minikube 上运行服务，您可以通过以下命令找到分配的 IP 地址和端口：
 {{< /note >}}

content/zh/docs/tasks/access-application-cluster/list-all-running-container-images.md

@@ -102,7 +102,7 @@ jsonpath 解释如下：
 
 {{< note >}}
 <!--
-**Note:** When fetching a single Pod by name, e.g. `kubectl get pod nginx`,
+When fetching a single Pod by name, e.g. `kubectl get pod nginx`,
 the `.items[*]` portion of the path should be omitted because a single
 Pod is returned instead of a list of items.
 -->

content/zh/docs/tasks/access-application-cluster/load-balance-access-application-cluster.md

@@ -109,7 +109,7 @@ load-balanced access to an application running in a cluster.
 
    {{< note >}}
 <!--
-   **Note:** If you are using Minikube, you don't get an external IP address. The
+    If you are using Minikube, you don't get an external IP address. The
    external IP address remains in the pending state.
 -->
    **注意：** 如果您使用 Minikube，那么您将不会获得外部 IP 地址。外部 IP 地址将保持 pending 状态。
@@ -139,7 +139,7 @@ load-balanced access to an application running in a cluster.
 
    {{< note >}}
 <!--
-   **Note:** If you are using Minikube, enter these commands:
+   If you are using Minikube, enter these commands:
 -->
    **注意：** 如果您使用 Minikube，输入以下命令：
    {{< /note >}}

content/zh/docs/tasks/access-application-cluster/port-forward-access-application-cluster.md

@@ -200,7 +200,7 @@ local workstation to debug the database that is running in the pod.
 
 {{< warning >}}
 <!--
-**Warning**: Due to known limitations, port forward today only works for TCP protocol.
+Due to known limitations, port forward today only works for TCP protocol.
 The support to UDP protocol is being tracked in
 [issue 47862](https://github.com/kubernetes/kubernetes/issues/47862).
 -->

content/zh/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade-1-9.md

@@ -54,7 +54,7 @@ Before proceeding:
 {{< caution >}}
 <!--
 
-**Caution:** All the containers will get restarted after the upgrade, due to container spec hash value gets changed.
+All the containers will get restarted after the upgrade, due to container spec hash value gets changed.
 
 --->
 **注意:** 由于容器的具体哈希值改变了，所有的容器在升级之后会重新启动。
@@ -98,7 +98,7 @@ chmod a+rx /usr/bin/kubeadm
 {{< caution >}}
 <!--
 
-**Caution:** Upgrading the `kubeadm` package on your system prior to upgrading the control plane causes a failed upgrade. 
+Upgrading the `kubeadm` package on your system prior to upgrading the control plane causes a failed upgrade. 
 Even though `kubeadm` ships in the Kubernetes repositories, it's important to install `kubeadm` manually. The kubeadm 
 team is working on fixing this limitation. 
 

content/zh/docs/tasks/administer-cluster/sysctl-cluster.md

@@ -103,7 +103,7 @@ The following sysctls are supported in the _safe_ set:
 
 {{< note >}}
 <!--
-**Note**: The example `net.ipv4.tcp_syncookies` is not namespaced on Linux kernel version 4.4 or lower.
+The example `net.ipv4.tcp_syncookies` is not namespaced on Linux kernel version 4.4 or lower.
 --->
 **注意**: 示例中的 `net.ipv4.tcp_syncookies` 在Linux 内核 4.4 或更低的版本中是无命名空间的。
 {{< /note >}}
@@ -226,7 +226,7 @@ spec:
 
 {{< warning >}}
 <!--
-**Warning**: Due to their nature of being _unsafe_, the use of _unsafe_ sysctls
+Due to their nature of being _unsafe_, the use of _unsafe_ sysctls
 is at-your-own-risk and can lead to severe problems like wrong behavior of
 containers, resource shortage or complete breakage of a node.
 --->
@@ -299,7 +299,7 @@ given sysctl is both allowed and forbidden.
 
 {{< warning >}}
 <!--
-**Warning**: If you whitelist unsafe sysctls via the `allowedUnsafeSysctls` field
+If you whitelist unsafe sysctls via the `allowedUnsafeSysctls` field
 in a PodSecurityPolicy, any pod using such a sysctl will fail to start
 if the sysctl is not whitelisted via the `--allowed-unsafe-sysctls` kubelet
 flag as well on that node.

content/zh/docs/tasks/debug-application-cluster/audit.md

@@ -79,7 +79,7 @@ Each request can be recorded with an associated "stage". The known stages are:
 
 {{< note >}}
 <!--
-**Note** The audit logging feature increases the memory consumption of the API
+The audit logging feature increases the memory consumption of the API
 server because some context required for auditing is stored for each request.
 Additionally, memory consumption depends on the audit logging configuration.
 -->
@@ -174,7 +174,7 @@ In both cases, audit events structure is defined by the API in the
 
 {{< note >}}
 <!--
-**Note:** In case of patches, request body is a JSON array with patch operations, not a JSON object
+In case of patches, request body is a JSON array with patch operations, not a JSON object
 with an appropriate Kubernetes API object. For example, the following request body is a valid patch
 request to `/apis/batch/v1/namespaces/some-namespace/jobs/some-job-name`.
 -->

content/zh/docs/tasks/inject-data-application/downward-api-volume-expose-pod-information.md

@@ -184,7 +184,7 @@ kubectl exec -it kubernetes-downwardapi-volume-example-2 -- sh
 * Pod的注释
 
 {{< note >}}
-**Note:** 如果容器未指定CPU和memory limits，则Downward API默认为节点可分配值。
+如果容器未指定CPU和memory limits，则Downward API默认为节点可分配值。
 {{< /note >}}
 
 ## 投射密钥到指定路径并且指定文件权限