Add admonition type to shortcode (#9482)

* Change existing admon blocks

* Fix includes issue

content/en/docs/tasks/access-application-cluster/configure-access-multiple-clusters.md

@@ -13,7 +13,7 @@ one or more configuration files, you can quickly switch between clusters by usin
 `kubectl config use-context` command.
 
 {{< note >}}
-**Note:** A file that is used to configure access to a cluster is sometimes called
+A file that is used to configure access to a cluster is sometimes called
 a *kubeconfig file*. This is a generic way of referring to configuration files.
 It does not mean that there is a file named `kubeconfig`.
 {{< /note >}}

content/en/docs/tasks/access-application-cluster/configure-cloud-provider-firewall.md

@@ -84,12 +84,11 @@ gcloud compute firewall-rules create my-rule --allow=tcp:<port>
 ```
 
 {{< note >}}
-**Note**: GCE firewalls are defined per-vm, rather than per-ip
-address. This means that when you open a firewall for a service's ports,
-anything that serves on that port on that VM's host IP address may potentially
-serve traffic.  Note that this is not a problem for other Kubernetes services,
-as they listen on IP addresses that are different than the host node's external
-IP address.
+GCE firewalls are defined per-vm, rather than per-ip address. This means that
+when you open a firewall for a service's ports, anything that serves on that
+port on that VM's host IP address may potentially serve traffic. Note that this
+is not a problem for other Kubernetes services, as they listen on IP addresses
+that are different than the host node's external IP address.
 
 Consider:
 

content/en/docs/tasks/access-application-cluster/connecting-frontend-backend.md

@@ -148,11 +148,13 @@ deployment.apps/frontend created
 service/frontend created
 ```
 
-{{< note >}}**Note:** The nginx configuration is baked into the
-[container image](/examples/service/access/Dockerfile).
-A better way to do this would be to use a
-[ConfigMap](/docs/tasks/configure-pod-container/configure-pod-configmap/), so
-you can change the configuration more easily.{{< /note >}}
+{{< note >}}
+The nginx configuration is baked into the [container
+image](/examples/service/access/Dockerfile). A better way to do this would
+be to use a
+[ConfigMap](/docs/tasks/configure-pod-container/configure-pod-configmap/),
+so that you can change the configuration more easily.
+{{< /note >}}
 
 ### Interact with the frontend Service
 

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

@@ -108,8 +108,9 @@ which should produce output like this:
 The IP address is listed next to `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:
 {{< /note >}}
+
 ```bash
 minikube service example-service --url
 ```
@@ -181,7 +182,7 @@ compared to the `service.spec.externalTrafficPolicy` field. The values match as
 * "Global" for annotation <-> "Cluster" for field
 
 {{< note >}}
-**Note:** This feature is not currently implemented for all cloudproviders/environments.
+This feature is not currently implemented for all cloudproviders/environments.
 {{< /note >}}
 
 Known issues:

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

@@ -63,7 +63,7 @@ The jsonpath is interpreted as follows:
 - `.image`: get the image
 
 {{< 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.
 {{< /note >}}

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

@@ -71,7 +71,7 @@ load-balanced access to an application running in a cluster.
    command.
 
    {{< 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.
    {{< /note >}}
 
@@ -90,7 +90,7 @@ load-balanced access to an application running in a cluster.
        Hello Kubernetes!
 
    {{< note >}}
-   **Note:** If you are using Minikube, enter these commands:
+   If you are using Minikube, enter these commands:
    {{< /note >}}
 
        kubectl cluster-info

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

@@ -137,7 +137,7 @@ is running the Redis server. With this connection in place you can use your
 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).
 {{< /warning >}}