From 7a6af682a89655038c5b10ab0286268b96cd44b1 Mon Sep 17 00:00:00 2001 From: Sebastiaan van Steenis Date: Tue, 26 Mar 2019 00:55:28 +0100 Subject: [PATCH] Add note on Volume Claim Template in workloads --- .../v2.x/en/k8s-in-rancher/workloads/deploy-workloads/_index.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/rancher/v2.x/en/k8s-in-rancher/workloads/deploy-workloads/_index.md b/content/rancher/v2.x/en/k8s-in-rancher/workloads/deploy-workloads/_index.md index b02a218e569..ab046ce7d06 100644 --- a/content/rancher/v2.x/en/k8s-in-rancher/workloads/deploy-workloads/_index.md +++ b/content/rancher/v2.x/en/k8s-in-rancher/workloads/deploy-workloads/_index.md @@ -33,6 +33,8 @@ Deploy a workload to run an application in one or more containers. Use this section to add storage for your workload. You can manually specify the volume that you want to add, use a persistent volume claim to dynamically create a volume for the workload, or read data for a volume to use from a file such as a [ConfigMap]({{< baseurl >}}/rancher/v2.x/en/k8s-in-rancher/configmaps/). + When you are deploying a Stateful Set, you should use a Volume Claim Template when using Persistent Volumes. This will ensure that Persistent Volumes are created dynamically when you scale your Stateful Set. This option is available in the UI as of Rancher v2.2.0. + - **Scaling/Upgrade Policy** >**Amazon Note for Volumes:**