From 065efcb313583f2e4430d607c25290f5b33e5dd4 Mon Sep 17 00:00:00 2001
From: vishakha <54327666+vishakhanihore@users.noreply.github.com>
Date: Tue, 15 Oct 2019 04:05:51 +0530
Subject: [PATCH] Completeing AzureDisk storage class parameters (#16841)

---
 content/en/docs/concepts/storage/storage-classes.md | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/content/en/docs/concepts/storage/storage-classes.md b/content/en/docs/concepts/storage/storage-classes.md
index dc75e2433d826..c071d14faacdc 100644
--- a/content/en/docs/concepts/storage/storage-classes.md
+++ b/content/en/docs/concepts/storage/storage-classes.md
@@ -611,6 +611,9 @@ parameters:
   unmanaged disk in the same resource group as the cluster. When `kind` is 
   `managed`, all managed disks are created in the same resource group as 
   the cluster.
+* `resourceGroup`: Specify the resource group in which the Azure disk will be created. 
+   It must be an existing resource group name. If it is unspecified, the disk will be 
+   placed in the same resource group as the current Kubernetes cluster.
 
 - Premium VM can attach both Standard_LRS and Premium_LRS disks, while Standard
   VM can only attach Standard_LRS disks.