Update images with specified width to use figure shortcode (#8475)
Hugo does not support the way the image's max-width was specified before. This fix will constrain images to always be 50% rather than max out at 50%, but it is the best we can easily do for now. Signed-off-by: Misty Stanley-Jones <mistyhacks@google.com>pull/8479/head
parent
98e6173052
commit
f7d157ecbf
|
@ -38,7 +38,7 @@ Pods are designed to support multiple cooperating processes (as containers) that
|
|||
|
||||
Note that grouping multiple co-located and co-managed containers in a single Pod is a relatively advanced use case. You should use this pattern only in specific instances in which your containers are tightly coupled. For example, you might have a container that acts as a web server for files in a shared volume, and a separate "sidecar" container that updates those files from a remote source, as in the following diagram:
|
||||
|
||||
{: style="max-width: 50%" }
|
||||
{{< figure src="/images/docs/pod.svg" title="pod diagram" width="50%" >}}
|
||||
|
||||
Pods provide two kinds of shared resources for their constituent containers: *networking* and *storage*.
|
||||
|
||||
|
|
|
@ -58,7 +58,7 @@ that means that it exists as long as that pod (with that UID) exists. If that
|
|||
pod is deleted for any reason, even if an identical replacement is created, the
|
||||
related thing (e.g. volume) is also destroyed and created anew.
|
||||
|
||||
{: style="max-width: 50%" }
|
||||
{{< figure src="//images/docs/pod.svg" title="pod diagram" width="50%" >}}
|
||||
|
||||
*A multi-container pod that contains a file puller and a
|
||||
web server that uses a persistent volume for shared storage between the containers.*
|
||||
|
|
Loading…
Reference in New Issue