Add admonition type to shortcode (#9482)

* Change existing admon blocks * Fix includes issue
2018-11-06 11:33:04 -08:00
parent e839031292
commit d65e1790ff
192 changed files with 673 additions and 543 deletions
@@ -31,7 +31,9 @@ You need 2 or more machines with Fedora installed.
 }
 ```

-**NOTE:** Choose an IP range that is *NOT* part of the public IP address range.
+{{< note >}}
+Choose an IP range that is *NOT* part of the public IP address range.
+{{< /note >}}

 Add the configuration to the etcd server on fed-master.

@@ -71,7 +73,9 @@ FLANNEL_ETCD_KEY="/coreos.com/network"
 FLANNEL_OPTIONS=""
 ```

-**Note:** By default, flannel uses the interface for the default route. If you have multiple interfaces and would like to use an interface other than the default route one, you could add "-iface=" to FLANNEL_OPTIONS. For additional options, run `flanneld --help` on command line.
+{{< note >}}
+By default, flannel uses the interface for the default route. If you have multiple interfaces and would like to use an interface other than the default route one, you could add "-iface=" to FLANNEL_OPTIONS. For additional options, run `flanneld --help` on command line.
+{{< /note >}}

 Enable the flannel service.

@@ -117,6 +117,7 @@ juju run-action new-etcd/0 restore
 {{% /capture %}}

 {{% capture discussion %}}
+
 ## Known Limitations

 #### Loss of PKI warning
@@ -126,10 +127,9 @@ all TLS pki will be lost. No PKI migration occurs outside
 of the units requesting and registering the certificates.

 {{< caution >}}
-**Caution:**  Mismanaging this configuration will result in locking yourself
-out of the cluster, and can potentially break existing deployments in very
-strange ways relating to x509 validation of certificates, which affects both
-servers and clients.
+Mismanaging this configuration will result in locking yourself out of the cluster,
+and can potentially break existing deployments in very strange ways relating to x509
+validation of certificates, which affects both servers and clients.
 {{< /caution >}}

 #### Restoring from snapshot on a scaled cluster
@@ -12,7 +12,7 @@ This page shows you how to properly decommission a cluster.
 This page assumes you have a working Juju deployed cluster.

 {{< warning >}}
-**Warning:** By the time you've reached this step you should have backed up your workloads and pertinent data; this section is for the complete destruction of a cluster.
+By the time you've reached this step you should have backed up your workloads and pertinent data; this section is for the complete destruction of a cluster.
 {{< /warning >}}

 {{% /capture %}}
@@ -14,7 +14,7 @@ This page shows how the various network portions of a cluster work and how to co
 This page assumes you have a working Juju deployed cluster.

 {{< note >}}
-**Note:** Note that if you deploy a cluster via conjure-up or the CDK bundles, manually deploying CNI plugins is unnecessary.
+Note that if you deploy a cluster via conjure-up or the CDK bundles, manually deploying CNI plugins is unnecessary.
 {{< /note >}}
 {{% /capture %}}

@@ -43,8 +43,11 @@ loop     loop
 rootfs   rootfs    
 tmpfs    tmpfs
 ```
-> **Note**: This listing is for the Amazon Web Services public cloud.
-> Different clouds may have different pool names.
+
+{{< note >}}
+This listing is for the Amazon Web Services public cloud. Different clouds may have
+different pool names.
+{{< /note >}}

 Add a storage pool to the ceph-osd charm by NAME,SIZE,COUNT:

@@ -11,7 +11,7 @@ This page will outline how to manage and execute a Kubernetes upgrade.
 This page assumes you have a working deployed cluster.

 {{< warning >}}
-**Warning:** You should always back up all your data before attempting an upgrade.
+You should always back up all your data before attempting an upgrade.
 Don't forget to include the workload inside your cluster!
 Refer to the [backup documentation](/docs/getting-started-guides/ubuntu/backups).
 {{< /warning >}}
@@ -83,7 +83,7 @@ First you need to upgrade the masters:
    juju upgrade-charm kubernetes-master

 {{< note >}}
-**Note:** Always upgrade the masters before the workers.
+Always upgrade the masters before the workers.
 {{< /note >}}

 Once the latest charm is deployed, the channel for Kubernetes can be selected by issuing the following:
@@ -90,7 +90,7 @@ a deployed cluster. The following example will skip the `Flaky`, `Slow`, and
    juju run-action kubernetes-e2e/0 test skip='\[(Flaky|Slow|Feature:.*)\]'

 {{< note >}}
-**Note:** The escaping of the regex due to how bash handles brackets.
+The escaping of the regex due to how bash handles brackets.
 {{< /note >}}

 To see the different types of tests the Kubernetes end-to-end charm has access
@@ -112,7 +112,7 @@ command, as well as a flat file on disk on the `kubernetes-e2e` unit that
 executed the test.

 {{< note >}}
-**Note:** The results will only be available once the action has
+The results will only be available once the action has
 completed the test run. End-to-end testing can be quite time consuming, often
 taking more than 1 hour, depending on configuration.
 {{< /note >}}
@@ -3,7 +3,7 @@ title: Using Windows Server Containers in Kubernetes
 toc_hide: true
 ---
 {{< note >}}
-**Note:** These instructions were recently updated based on Windows Server platform enhancements and the Kubernetes v1.9 release
+These instructions were recently updated based on Windows Server platform enhancements and the Kubernetes v1.9 release
 {{< /note >}}

 Kubernetes version 1.5 introduced Alpha support for Windows Server
@@ -23,7 +23,7 @@ Containers on Kubernetes include:
 The Kubernetes control plane (API Server, Scheduler, Controller Manager, etc) continue to run on Linux, while the kubelet and kube-proxy can be run on Windows Server 2016 or later

 {{< note >}}
-**Note:** Windows Server Containers on Kubernetes is a Beta feature in Kubernetes v1.9
+Windows Server Containers on Kubernetes is a Beta feature in Kubernetes v1.9
 {{< /note >}}

 ## Get Windows Binaries
@@ -159,7 +159,7 @@ Note: this file assumes that a user previous created 'l2bridge' host networks on
 #### For 3. Open vSwitch (OVS) & Open Virtual Network (OVN) with Overlay

 {{< note >}}
-**Note:** Fully automated setup via Ansible playbooks is [available](https://github.com/openvswitch/ovn-kubernetes/tree/master/contrib).
+Fully automated setup via Ansible playbooks is [available](https://github.com/openvswitch/ovn-kubernetes/tree/master/contrib).
 {{< /note >}}

 For manual setup, continue the following steps.
@@ -264,7 +264,7 @@ Because your cluster has both Linux and Windows nodes, you must explicitly set t
 {{< codenew file="windows/simple-pod.yaml" >}}

 {{< note >}}
-**Note:** This example assumes you are running on Windows Server 1709, so uses the image tag to support that. If you are on a different version, you will need to update the tag. For example, if on Windows Server 2016, update to use `"image": "microsoft/iis"` which will default to that OS version.
+This example assumes you are running on Windows Server 1709, so uses the image tag to support that. If you are on a different version, you will need to update the tag. For example, if on Windows Server 2016, update to use `"image": "microsoft/iis"` which will default to that OS version.
 {{< /note >}}

 ### Secrets and ConfigMaps