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
@@ -120,7 +120,7 @@ cpu-demo                    974m         <something>
 Recall that by setting `-cpu "2"`, you configured the Container to attempt to use 2 CPUs, but the Container is only being allowed to use about 1 CPU. The Container CPU use is being throttled, because the Container is attempting to use more CPU resources than its limit.

 {{< note >}}
-**Note:** Another possible explanation for the CPU throttling is that the Node might not have
+Another possible explanation for the CPU throttling is that the Node might not have
 enough CPU resources available. Recall that the prerequisites for this exercise require each of
 your Nodes to have at least 1 CPU. If your Container runs on a Node that has only 1 CPU, the Container
 cannot use more than 1 CPU regardless of the CPU limit specified for the Container.
@@ -77,7 +77,7 @@ unless the Pod's grace period expires. For more details, see
 [Termination of Pods](/docs/user-guide/pods/#termination-of-pods).

 {{< note >}}
-**Note**: Kubernetes only sends the preStop event when a Pod is *terminated*.
+Kubernetes only sends the preStop event when a Pod is *terminated*.
 This means that the preStop hook is not invoked when the Pod is *completed*. 
 This limitation is tracked in [issue #55087](https://github.com/kubernetes/kubernetes/issues/55807).
 {{< /note >}}
@@ -189,7 +189,7 @@ annotation or the Pod’s specification, is applied to the first process run in
 each Container.

 {{< note >}}
-**Note**: When a Pod consumes a PersistentVolume, the GIDs associated with the
+When a Pod consumes a PersistentVolume, the GIDs associated with the
 PersistentVolume are not present on the Pod resource itself.
 {{< /note >}}

@@ -388,7 +388,7 @@ metadata:
 ## Configure all key-value pairs in a ConfigMap as container environment variables 

   {{< note >}}
-   **Note:** This functionality is available in Kubernetes v1.6 and later.
+   This functionality is available in Kubernetes v1.6 and later.
   {{< /note >}}

 1.  Create a ConfigMap containing multiple key-value pairs. 
@@ -516,7 +516,7 @@ special.type
 ```

 {{< caution >}}
-**Caution:** If there are some files in the `/etc/config/` directory, they will be deleted.
+If there are some files in the `/etc/config/` directory, they will be deleted.
 {{< /caution >}}

 ### Add ConfigMap data to a specific path in the Volume
@@ -563,7 +563,7 @@ basis. The [Secrets](/docs/concepts/configuration/secret/#using-secrets-as-files
 When a ConfigMap already being consumed in a volume is updated, projected keys are eventually updated as well. Kubelet is checking whether the mounted ConfigMap is fresh on every periodic sync. However, it is using its local ttl-based cache for getting the current value of the ConfigMap. As a result, the total delay from the moment when the ConfigMap is updated to the moment when new keys are projected to the pod can be as long as kubelet sync period + ttl of ConfigMaps cache in kubelet.

 {{< note >}}
-**Note:** A container using a ConfigMap as a
+A container using a ConfigMap as a
 [subPath](/docs/concepts/storage/volumes/#using-subpath) volume will not receive
 ConfigMap updates.
 {{< /note >}}
@@ -577,7 +577,7 @@ ConfigMap updates.
 The ConfigMap API resource stores configuration data as key-value pairs. The data can be consumed in pods or provide the configurations for system components such as controllers. ConfigMap is similar to [Secrets](/docs/concepts/configuration/secret/), but provides a means of working with strings that don't contain sensitive information. Users and system components alike can store configuration data in ConfigMap.

 {{< note >}}
-**Note:** ConfigMaps should reference properties files, not replace them. Think of the ConfigMap as representing something similar to the Linux `/etc` directory and its contents. For example, if you create a [Kubernetes Volume](/docs/concepts/storage/volumes/) from a ConfigMap, each data item in the ConfigMap is represented by an individual file in the volume.
+ConfigMaps should reference properties files, not replace them. Think of the ConfigMap as representing something similar to the Linux `/etc` directory and its contents. For example, if you create a [Kubernetes Volume](/docs/concepts/storage/volumes/) from a ConfigMap, each data item in the ConfigMap is represented by an individual file in the volume.
 {{< /note >}}

 The ConfigMap's `data` field contains the configuration data. As shown in the example below, this can be simple -- like individual properties defined using `--from-literal` -- or complex -- like configuration files or JSON blobs defined using `--from-file`.
@@ -618,7 +618,7 @@ data:
   This includes pods created via the Kubelet's --manifest-url flag, --config flag, or the Kubelet REST API.
   
   {{< note >}}
-   **Note:** These are not commonly-used ways to create pods.
+   These are not commonly-used ways to create pods.
   {{< /note >}}
   
 {{% /capture %}}
@@ -15,7 +15,7 @@ A service account provides an identity for processes that run in a Pod.
 [Cluster Admin Guide to Service Accounts](/docs/reference/access-authn-authz/service-accounts-admin/).*

 {{< note >}}
-**Note:** This document describes how service accounts behave in a cluster set up
+This document describes how service accounts behave in a cluster set up
 as recommended by the Kubernetes project.  Your cluster administrator may have
 customized the behavior in your cluster, in which case this documentation may
 not apply.
@@ -175,7 +175,7 @@ token:          ...
 ```

 {{< note >}}
-**Note:** The content of `token` is elided here.
+The content of `token` is elided here.
 {{< /note >}}

 ## Add ImagePullSecrets to a service account
@@ -254,7 +254,7 @@ TODO: Test and explain how to use additional non-K8s secrets with an existing se
 {{< feature-state for_k8s_version="v1.12" state="beta" >}}

 {{< note >}}
-**Note:** This ServiceAccountTokenVolumeProjection is __beta__ in 1.12 and
+This ServiceAccountTokenVolumeProjection is __beta__ in 1.12 and
 enabled by passing all of the following flags to the API server:

 * `--service-account-issuer`
@@ -53,7 +53,7 @@ The output contains a section similar to this:
 ```

 {{< note >}}
-**Note:** If you use a Docker credentials store, you won't see that `auth` entry but a `credsStore` entry with the name of the store as value.
+If you use a Docker credentials store, you won't see that `auth` entry but a `credsStore` entry with the name of the store as value.
 {{< /note >}}

 ## Create a Secret in the cluster that holds your authorization token
@@ -84,7 +84,7 @@ spec:
 ```

 {{< note >}}
-**Note:** If a Container specifies its own memory limit, but does not specify a memory request, Kubernetes
+If a Container specifies its own memory limit, but does not specify a memory request, Kubernetes
 automatically assigns a memory request that matches the limit. Similarly, if a Container specifies its own
 CPU limit, but does not specify a CPU request, Kubernetes automatically assigns a CPU request that matches
 the limit.
@@ -299,7 +299,7 @@ See [capability.h](https://github.com/torvalds/linux/blob/master/include/uapi/li
 for definitions of the capability constants.

 {{< note >}}
-**Note:** Linux capability constants have the form `CAP_XXX`. But when you list capabilities in your Container manifest, you must omit the `CAP_` portion of the constant. For example, to add `CAP_SYS_TIME`, include `SYS_TIME` in your list of capabilities.
+Linux capability constants have the form `CAP_XXX`. But when you list capabilities in your Container manifest, you must omit the `CAP_` portion of the constant. For example, to add `CAP_SYS_TIME`, include `SYS_TIME` in your list of capabilities.
 {{< /note >}}

 ## Assign SELinux labels to a Container
@@ -318,7 +318,7 @@ securityContext:
 ```

 {{< note >}}
-**Note:** To assign SELinux labels, the SELinux security module must be loaded on the host operating system.
+To assign SELinux labels, the SELinux security module must be loaded on the host operating system.
 {{< /note >}}

 ## Discussion
@@ -339,7 +339,7 @@ need to set the `level` section. This sets the
 label given to all Containers in the Pod as well as the Volumes.

 {{< warning >}}
-**Warning:** After you specify an MCS label for a Pod, all Pods with the same label can access the Volume. If you need inter-Pod protection, you must assign a unique MCS label to each Pod.
+After you specify an MCS label for a Pod, all Pods with the same label can access the Volume. If you need inter-Pod protection, you must assign a unique MCS label to each Pod.
 {{< /warning >}}

 {{% /capture %}}
@@ -296,7 +296,9 @@ INFO OpenShift file "foo-imagestream.yaml" created
 INFO OpenShift file "foo-buildconfig.yaml" created
 ```

-**Note**: If you are manually pushing the Openshift artifacts using ``oc create -f``, you need to ensure that you push the imagestream artifact before the buildconfig artifact, to workaround this Openshift issue: https://github.com/openshift/origin/issues/4518 .
+{{< note >}}
+If you are manually pushing the Openshift artifacts using ``oc create -f``, you need to ensure that you push the imagestream artifact before the buildconfig artifact, to workaround this Openshift issue: https://github.com/openshift/origin/issues/4518 .
+{{< /note >}}

 ## `kompose up`

@@ -335,6 +337,7 @@ pod/frontend-2768218532-cs5t5       1/1           Running       0            4m
 pod/redis-master-1432129712-63jn8   1/1           Running       0            4m
 pod/redis-slave-2504961300-nve7b    1/1           Running       0            4m
 ```
+
 **Note**:

 - You must have a running Kubernetes cluster with a pre-configured kubectl context.
@@ -550,7 +553,9 @@ The currently supported options are:
 | kompose.service.type | nodeport / clusterip / loadbalancer |
 | kompose.service.expose| true / hostname |

-**Note**: `kompose.service.type` label should be defined with `ports` only, otherwise `kompose` will fail.
+{{< note >}}
+The `kompose.service.type` label should be defined with `ports` only, otherwise `kompose` will fail.
+{{< /note >}}

 ## Restart

@@ -563,7 +568,9 @@ If you want to create normal pods without controllers you can use `restart` cons
 | `on-failure`               | Pod               | `OnFailure`         |
 | `no`                       | Pod               | `Never`             |

-**Note**: controller object could be `deployment` or `replicationcontroller`, etc.
+{{< note >}}
+The controller object could be `deployment` or `replicationcontroller`, etc.
+{{< /note >}}

 For e.g. `pival` service will become pod down here. This container calculated value of `pi`.