Update docs with subpath limitation (#7533)

This commit is contained in:
Michelle Au
2018-02-27 11:21:45 -08:00
committed by k8s-ci-robot
parent ab1398e940
commit 21926145fe
4 changed files with 31 additions and 0 deletions
+5
View File
@@ -338,6 +338,11 @@ However, it is using its local ttl-based cache for getting the current value of
As a result, the total delay from the moment when the secret is updated to the moment when new keys are
projected to the pod can be as long as kubelet sync period + ttl of secrets cache in kubelet.
**Note:** A container using a Secret as a
[subPath](/docs/concepts/storage/volumes#using-subpath) volume mount will not receive
Secret updates.
{: .note}
#### Using Secrets as Environment Variables
To use a secret in an environment variable in a pod:
+16
View File
@@ -211,6 +211,10 @@ its `log_level` entry are mounted into the Pod at path "`/etc/config/log_level`"
Note that this path is derived from the volume's `mountPath` and the `path`
keyed with `log_level`.
**Note:** A container using a ConfigMap as a [subPath](#using-subpath) volume mount will not
receive ConfigMap updates.
{: .note}
### csi
CSI stands for [Container Storage Interface](https://github.com/container-storage-interface/spec/blob/master/spec.md),
@@ -248,6 +252,10 @@ A CSI persistent volume has the following fields for users to specify:
A `downwardAPI` volume is used to make downward API data available to applications.
It mounts a directory and writes the requested data in plain text files.
**Note:** A container using Downward API as a [subPath](#using-subpath) volume mount will not
receive Downward API updates.
{: .note}
See the [`downwardAPI` volume example](/docs/tasks/inject-data-application/downward-api-volume-expose-pod-information/) for more details.
### emptyDir
@@ -687,6 +695,10 @@ parameters are nearly the same with two exceptions:
volume source. However, as illustrated above, you can explicitly set the `mode`
for each individual projection.
**Note:** A container using a projected volume source as a [subPath](#using-subpath) volume mount will not
receive updates for those volume sources.
{: .note}
### portworxVolume
A `portworxVolume` is an elastic block storage layer that runs hyperconverged with
@@ -807,6 +819,10 @@ non-volatile storage.
**Important:** You must create a secret in the Kubernetes API before you can use it.
{: .caution}
**Note:** A container using a Secret as a [subPath](#using-subpath) volume mount will not
receive Secret updates.
{: .note}
Secrets are described in more detail [here](/docs/user-guide/secrets).
### storageOS
@@ -476,6 +476,11 @@ 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:** A container using a ConfigMap as a
[subPath](/docs/concepts/storage/volumes/#using-subpath) volume will not receive
ConfigMap updates.
{: .note}
{% endcapture %}
{% capture discussion %}
@@ -135,6 +135,11 @@ written to a new temporary directory, and the `..data` symlink is updated
atomically using
[rename(2)](http://man7.org/linux/man-pages/man2/rename.2.html).
**Note:** A container using Downward API as a
[subPath](/docs/concepts/storage/volumes/#using-subpath) volume mount will not
receive Downward API updates.
{: .note}
Exit the shell:
```shell