Add admonition type to shortcode (#9482)

* Change existing admon blocks

* Fix includes issue

content/en/docs/setup/independent/create-cluster-kubeadm.md

@@ -99,7 +99,7 @@ timeframe; which also applies to `kubeadm`.
 See ["Installing kubeadm"](/docs/setup/independent/install-kubeadm/).
 
 {{< note >}}
-**Note:** If you have already installed kubeadm, run `apt-get update &&
+If you have already installed kubeadm, run `apt-get update &&
 apt-get upgrade` or `yum update` to get the latest version of kubeadm.
 
 When you upgrade, the kubelet restarts every few seconds as it waits in a crashloop for
@@ -228,7 +228,7 @@ created, and deleted with the `kubeadm token` command. See the
 ### Installing a pod network add-on {#pod-network}
 
 {{< caution >}}
-**Caution:** This section contains important information about installation and deployment order. Read it carefully before proceeding.
+This section contains important information about installation and deployment order. Read it carefully before proceeding.
 {{< /caution >}}
 
 You must install a pod network add-on so that your pods can communicate with
@@ -465,7 +465,7 @@ The output is similar to this:
 ```
 
 {{< note >}}
-**Note:** To specify an IPv6 tuple for `<master-ip>:<master-port>`, IPv6 address must be enclosed in square brackets, for example: `[fd00::101]:2073`.
+To specify an IPv6 tuple for `<master-ip>:<master-port>`, IPv6 address must be enclosed in square brackets, for example: `[fd00::101]:2073`.
 {{< /note >}}
 
 The output should look something like:
@@ -498,7 +498,7 @@ kubectl --kubeconfig ./admin.conf get nodes
 ```
 
 {{< note >}}
-**Note:** The example above assumes SSH access is enabled for root. If that is not the
+The example above assumes SSH access is enabled for root. If that is not the
 case, you can copy the `admin.conf` file to be accessible by some other user
 and `scp` using that other user instead.
 

content/en/docs/setup/independent/high-availability.md

@@ -22,9 +22,9 @@ with upgrading your clusters, for example. We encourage you to try either approa
 and provide feedback.
 
 {{< caution >}}
-**Caution**: This page does not address running your cluster on a cloud provider.
-In a cloud environment, neither approach documented here works with Service objects
-of type LoadBalancer, or with dynamic PersistentVolumes.
+This page does not address running your cluster on a cloud provider. In a cloud
+environment, neither approach documented here works with Service objects of type
+LoadBalancer, or with dynamic PersistentVolumes.
 {{< /caution >}}
 
 {{% /capture %}}
@@ -49,9 +49,8 @@ For the external etcd cluster only, you also need:
 - Three additional machines for etcd members
 
 {{< note >}}
-**Note**: The following examples run Calico as the Pod networking provider. If
-you run another networking provider, make sure to replace any default values as
-needed.
+The following examples run Calico as the Pod networking provider. If you run another
+networking provider, make sure to replace any default values as needed.
 {{< /note >}}
 
 {{% /capture %}}
@@ -61,8 +60,7 @@ needed.
 ## First steps for both methods
 
 {{< note >}}
-**Note**: All commands in this guide on any control plane or etcd node should be
-run as root.
+All commands in this guide on any control plane or etcd node should be run as root.
 {{< /note >}}
 
 - Find your pod CIDR. For details, see [the CNI network
@@ -102,9 +100,8 @@ run as root.
 ### Create load balancer for kube-apiserver
 
 {{< note >}}
-**Note**: There are many configurations for load balancers. The following
-example is only one option. Your cluster requirements may need a
-different configuration.
+There are many configurations for load balancers. The following example is only one
+option. Your cluster requirements may need a different configuration.
 {{< /note >}}
 
 1.  Create a kube-apiserver load balancer with a name that resolves to DNS.
@@ -140,7 +137,7 @@ different configuration.
 ### Bootstrap the first stacked control plane node
 
 {{< note >}}
-**Note**: Optionally replace `stable` with a different version of Kubernetes, for example `v1.12.0`.
+Optionally replace `stable` with a different version of Kubernetes, for example `v1.12.0`.
 {{< /note >}}
 
 1.  Create a `kubeadm-config.yaml` template file:
@@ -217,7 +214,7 @@ done
 ```
 
 {{< note >}}
-**Note**: Remember that your config may differ from this example.
+Remember that your config may differ from this example.
 {{< /note >}}
 
 ### Add the second stacked control plane node
@@ -439,7 +436,7 @@ done
 1.  Create a `kubeadm-config.yaml`:
 
 {{< note >}}
-**Note**: Optionally replace `stable` with a different version of Kubernetes, for example `v1.11.3`.
+Optionally replace `stable` with a different version of Kubernetes, for example `v1.11.3`.
 {{< /note >}}
 
         apiVersion: kubeadm.k8s.io/v1alpha3

content/en/docs/setup/independent/setup-ha-etcd-with-kubeadm.md

@@ -38,7 +38,7 @@ The general approach is to generate all certs on one node and only distribute
 the *necessary* files to the other nodes.
 
 {{< note >}}
-**Note:**  kubeadm contains all the necessary crytographic machinery to generate
+kubeadm contains all the necessary crytographic machinery to generate
 the certificates described below; no other cryptographic tooling is required for
 this example.
 {{< /note >}}

content/en/docs/setup/independent/troubleshooting-kubeadm.md

@@ -259,7 +259,7 @@ kubectl -n kube-system get deployment coredns -o yaml | \
 ```
 
 {{< warning >}}
-**Warning**: Disabling SELinux or setting `allowPrivilegeEscalation` to `true` can compromise
+Disabling SELinux or setting `allowPrivilegeEscalation` to `true` can compromise
 the security of your cluster.
 {{< /warning >}}