From c613b5467189cd22c4312bc361f329b808456408 Mon Sep 17 00:00:00 2001
From: Dr Luke Angel <a@lukeangel.co>
Date: Sun, 17 Feb 2019 19:38:57 -0600
Subject: [PATCH] Updated ReadMe (#11967)

* Updated ReadMe

Added windows commands

* Update configure-access-multiple-clusters.md

* Update configure-access-multiple-clusters.md

* Update configure-access-multiple-clusters.md
---
 .../configure-access-multiple-clusters.md     | 30 +++++++++++++++----
 1 file changed, 24 insertions(+), 6 deletions(-)

diff --git a/content/en/docs/tasks/access-application-cluster/configure-access-multiple-clusters.md b/content/en/docs/tasks/access-application-cluster/configure-access-multiple-clusters.md
index cb8b67e557..21bb003f3c 100644
--- a/content/en/docs/tasks/access-application-cluster/configure-access-multiple-clusters.md
+++ b/content/en/docs/tasks/access-application-cluster/configure-access-multiple-clusters.md
@@ -251,22 +251,31 @@ The preceding configuration file defines a new context named `dev-ramp-up`.
 
 See whether you have an environment variable named `KUBECONFIG`. If so, save the
 current value of your `KUBECONFIG` environment variable, so you can restore it later.
-For example, on Linux:
+For example:
 
+### Linux
 ```shell
 export  KUBECONFIG_SAVED=$KUBECONFIG
 ```
-
+### Windows PowerShell
+```shell
+ $Env:KUBECONFIG_SAVED=$ENV:KUBECONFIG
+ ```
  The `KUBECONFIG` environment variable is a list of paths to configuration files. The list is
 colon-delimited for Linux and Mac, and semicolon-delimited for Windows. If you have
 a `KUBECONFIG` environment variable, familiarize yourself with the configuration files
 in the list.
 
-Temporarily append two paths to your `KUBECONFIG` environment variable. For example, on Linux:
+Temporarily append two paths to your `KUBECONFIG` environment variable. For example:<br>
 
+### Linux
 ```shell
 export  KUBECONFIG=$KUBECONFIG:config-demo:config-demo-2
 ```
+### Windows PowerShell
+```shell
+$Env:KUBECONFIG_SAVED=(config-demo;config-demo-2)
+```
 
 In your `config-exercise` directory, enter this command:
 
@@ -320,11 +329,16 @@ familiarize yourself with the contents of these files.
 
 If you have a `$HOME/.kube/config` file, and it's not already listed in your
 `KUBECONFIG` environment variable, append it to your `KUBECONFIG` environment variable now.
-For example, on Linux:
+For example:
 
+### Linux
 ```shell
 export KUBECONFIG=$KUBECONFIG:$HOME/.kube/config
 ```
+### Windows Powershell
+```shell
+ $Env:KUBECONFIG=($Env:KUBECONFIG;$HOME/.kube/config)
+```
 
 View configuration information merged from all the files that are now listed
 in your `KUBECONFIG` environment variable. In your config-exercise directory, enter:
@@ -335,11 +349,15 @@ kubectl config view
 
 ## Clean up
 
-Return your `KUBECONFIG` environment variable to its original value. For example, on Linux:
-
+Return your `KUBECONFIG` environment variable to its original value. For example:<br>
+Linux:
 ```shell
 export KUBECONFIG=$KUBECONFIG_SAVED
 ```
+Windows PowerShell
+```shell
+ $Env:KUBECONFIG=$ENV:KUBECONFIG_SAVED
+```
 
 {{% /capture %}}