[Dev Spaces] remove portal create

Author: zr-msft

articles/dev-spaces/get-started-netcore-visualstudio.md

@@ -20,28 +20,59 @@ In this guide, you will learn how to:
 > [!Note]
 > **If you get stuck** at any time, see the [Troubleshooting](troubleshooting.md) section.
 
+## Install the Azure CLI
+Azure Dev Spaces requires minimal local machine setup. Most of your dev space's configuration gets stored in the cloud, and is shareable with other users. Start by downloading and running the [Azure CLI](/cli/azure/install-azure-cli?view=azure-cli-latest).
 
-## Create a Kubernetes cluster enabled for Azure Dev Spaces
+### Sign in to Azure CLI
+Sign in to Azure. Type the following command in a terminal window:
+
+```azurecli
+az login
+```
+
+> [!Note]
+> If you don't have an Azure subscription, you can create a [free account](https://azure.microsoft.com/free).
+
+#### If you have multiple Azure subscriptions...
+You can view your subscriptions by running: 
 
-1. Sign in to the Azure portal at https://portal.azure.com.
-1. Choose **Create a resource** > search for **Kubernetes** > select **Kubernetes Service** > **Create**.
+```azurecli
+az account list --output table
+```
 
-   Complete the following steps under each heading of the *Create Kubernetes cluster* form and verify your selected [region supports Azure Dev Spaces][supported-regions].
+Locate the subscription which has *True* for *IsDefault*.
+If this isn't the subscription you want to use, you can change the default subscription:
 
-   - **PROJECT DETAILS**: select an Azure subscription and a new or existing Azure resource group.
-   - **CLUSTER DETAILS**: enter a name, region, version, and DNS name prefix for the AKS cluster.
-   - **SCALE**: select a VM size for the AKS agent nodes and the number of nodes. If you’re getting started with Azure Dev Spaces, one node is enough to explore all the features. The node count can be easily adjusted any time after the cluster is deployed. Note that the VM size can’t be changed once an AKS cluster has been created. However, once an AKS cluster has been deployed, you can easily create a new AKS cluster with larger VMs and use Dev Spaces to redeploy to that larger cluster if you need to scale up.
+```azurecli
+az account set --subscription <subscription ID>
+```
 
-   ![Kubernetes configuration settings](media/common/Kubernetes-Create-Cluster-2.PNG)
+## Create a Kubernetes cluster enabled for Azure Dev Spaces
 
+At the command prompt, create the resource group in a [region that supports Azure Dev Spaces][supported-regions].
 
-   Select **Next: Authentication** when complete.
+```azurecli
+az group create --name MyResourceGroup --location <region>
+```
 
-1. Choose your desired setting for Role-based Access Control (RBAC). Azure Dev Spaces supports clusters with RBAC enabled, or disabled.
+Create a Kubernetes cluster with the following command:
 
-    ![RBAC setting](media/common/k8s-RBAC.PNG)
+```azurecli
+az aks create -g MyResourceGroup -n MyAKS --location <region> --generate-ssh-keys
+```
 
-1. Select **Review + create** and then **Create** when complete.
+It takes a few minutes to create the cluster.
+
+### Configure your AKS cluster to use Azure Dev Spaces
+
+Enter the following Azure CLI command, using the resource group that contains your AKS cluster, and your AKS cluster name. The command configures your cluster with support for Azure Dev Spaces.
+
+   ```azurecli
+   az aks use-dev-spaces -g MyResourceGroup -n MyAKS
+   ```
+   
+> [!IMPORTANT]
+> The Azure Dev Spaces configuration process will remove the `azds` namespace in the cluster, if it exists.
 
 ## Get the Visual Studio tools
 Install the latest version of [Visual Studio 2019](https://www.visualstudio.com/vs/) on Windows with the Azure Development workload.

articles/dev-spaces/how-dev-spaces-works-cluster-setup.md

@@ -13,7 +13,7 @@ Azure Dev Spaces provides you with multiple ways to rapidly iterate and debug Ku
 
 ## Prepare your AKS cluster
 
-To prepare your AKS cluster for Dev Spaces, verify your AKS cluster is in a region [supported by Azure Dev Spaces][supported-regions] and you are running Kubernetes 1.10.3 or later. To enable Azure Dev Spaces on your cluster from the Azure portal, navigate to your cluster, click *Dev Spaces*, change *Use Dev Spaces* to *Yes*, and click *Save*. You can also enable Azure Dev Spaces from the Azure CLI by running `az aks use-dev-spaces`.
+To prepare your AKS cluster for Dev Spaces, verify your AKS cluster is in a region [supported by Azure Dev Spaces][supported-regions] and you are running Kubernetes 1.10.3 or later. You can enable Azure Dev Spaces from the Azure CLI by running `az aks use-dev-spaces`.
 
 For an example of setting up an AKS cluster for Dev Spaces, see the [team development quickstart][quickstart-team].
 

articles/dev-spaces/how-to/dev-spaces-business-continuity.md

@@ -21,14 +21,6 @@ Enabling Dev Spaces on AKS clusters in different regions allows you to resume us
 
 For general information about multi-region deployments of AKS, see [Plan for multi-region deployment](https://docs.microsoft.com/azure/aks/operator-best-practices-multi-region#plan-for-multiregion-deployment)
 
-### Enable Dev Spaces via the Azure portal
-
-Select the **Dev Spaces** menu item under the settings of each cluster in the Azure portal. Then choose the option to enable Dev Spaces and save.
-
-![Enabling Dev Spaces via Azure portal](../media/common/enable-dev-spaces.jpg)
-
-Repeat this process for each cluster.
-
 ### Enable Dev Spaces via the Azure CLI
 
 You can also enable Dev Spaces at the command line:

articles/dev-spaces/how-to/install-dev-spaces.md

@@ -55,24 +55,6 @@ Deleting Azure Dev Spaces Controller 'MyAKS' in resource group 'MyResourceGroup'
 
 The above command removes Azure Dev Spaces from the *MyAKS* cluster in *MyResourceGroup*. Any namespaces you created with Azure Dev Spaces will remain along with their workloads, but new workloads in those namespaces will not be instrumented with Azure Dev Spaces. In addition, if you restart any existing pods instrumented with Azure Dev Spaces, you may see errors. Those pods must be redeployed without Azure Dev Spaces tooling. To fully remove Azure Dev Spaces from your cluster, delete all pods in all namespaces where Azure Dev Spaces was enabled.
 
-## Enable or remove Azure Dev Spaces using the Azure portal
-
-Before you can enable Dev Spaces using the Azure portal, you need:
-* An Azure subscription. If you don't have an Azure subscription, you can create a [free account][az-portal-create-account].
-* [An AKS cluster][create-aks-portal] in a [supported region][supported-regions].
-
-To enable Azure Dev Spaces using the Azure portal:
-1. Sign in to the [Azure portal][az-portal].
-1. Navigate to your AKS cluster.
-1. Select the *Dev Spaces* menu item.
-1. Change *Enable Dev Spaces* to *Yes* and click *Save*.
-
-![Enable Dev Spaces in the Azure portal](../media/how-to-setup-dev-spaces/enable-dev-spaces-portal.png)
-
-Enabling Azure Dev Spaces using the Azure portal **does not** install any client-side tools for Azure Dev Spaces.
-
-To remove Azure Dev Spaces from your AKS cluster, change *Enable Dev Spaces* to *No* and click *Save*. Any namespaces you created with Azure Dev Spaces will remain along with their workloads, but new workloads in those namespaces will not be instrumented with Azure Dev Spaces. In addition, if you restart any existing pods instrumented with Azure Dev Spaces, you may see errors. Those pods must be redeployed without Azure Dev Spaces tooling. To fully remove Azure Dev Spaces from your cluster, delete all pods in all namespaces where Azure Dev Spaces was enabled.
-
 ## Install the client-side tools
 
 You can use the Azure Dev Spaces client-side tools to interact with dev spaces on an AKS cluster from your local machine. There are several ways to install the client-side tools:
@@ -89,7 +71,6 @@ Learn how Azure Dev Spaces helps you develop more complex applications across mu
 > [Team development in Azure Dev Spaces][team-development-qs]
 
 [create-aks-cli]: ../../aks/kubernetes-walkthrough.md#create-a-resource-group
-[create-aks-portal]: ../../aks/kubernetes-walkthrough-portal.md#create-an-aks-cluster
 [install-cli]: /cli/azure/install-azure-cli?view=azure-cli-latest
 [supported-regions]: https://azure.microsoft.com/global-infrastructure/services/?products=kubernetes-service
 [team-development-qs]: ../quickstart-team-development.md

articles/dev-spaces/how-vs-code-works-with-dev-spaces.md

@@ -30,7 +30,7 @@ The Dockerfile, Helm chart, and `azds.yaml` files are the same assets generated
 
 After you generate the assets for your project, you can run your Java, Node.js, and .NET Core services in an existing dev space from Visual Studio Code. In the *Debug* page of Visual Studio Code, you can invoke the launch configuration from the `.vscode` directory to run your project.
 
-You must create your AKS cluster and enable Azure Dev Spaces in your cluster outside of Visual Studio Code. For example, you can use the Azure CLI or the Azure portal to do this setup. You can reuse existing Dockerfiles, Helm charts, and `azds.yaml` files created outside of Visual Studio Code, such as the assets generated by running `azds prep`. If you do reuse assets generated outside of Visual Studio Code, you still need to have a `.vscode` directory. This `.vscode` directory can be regenerated by Visual Studio code and the Azure Dev Spaces extension and will not overwrite your existing assets.
+You must create your AKS cluster and enable Azure Dev Spaces in your cluster outside of Visual Studio Code. You can reuse existing Dockerfiles, Helm charts, and `azds.yaml` files created outside of Visual Studio Code, such as the assets generated by running `azds prep`. If you do reuse assets generated outside of Visual Studio Code, you still need to have a `.vscode` directory. This `.vscode` directory can be regenerated by Visual Studio code and the Azure Dev Spaces extension and will not overwrite your existing assets.
 
 For .NET Core projects, you must have the [C# extension][csharp-extension] installed to run your .NET service from Visual Studio Code. Also for Java projects using Maven, you must have the [Java Debugger for Azure Dev Spaces extension][java-extension] installed as well as [Maven installed and configured][maven] to run your Java service from Visual Studio Code.