incorporate Anthony's comments

Author: mumian

articles/aks/TOC.yml

@@ -25,7 +25,7 @@
           href: learn/quick-kubernetes-deploy-powershell.md
         - name: Use the Azure portal
           href: learn/quick-kubernetes-deploy-portal.md
-        - name: Use Bicep extension
+        - name: Use Bicep Kubernetes provider
           displayName: Resource Manager,arm,template
           href: learn/quick-kubernetes-deploy-bicep-extensibility-kubernetes-provider.md
         - name: Use Bicep

articles/aks/learn/quick-kubernetes-deploy-bicep-extensibility-kubernetes-provider.md

@@ -3,7 +3,7 @@ title: Quickstart - Deploy Azure applications to Azure Kubernetes Services by us
 description: Learn how to quickly create a Kubernetes cluster and deploy Azure applications in Azure Kubernetes Service (AKS) by using Bicep extensibility Kubernetes provider.
 services: container-service
 ms.topic: quickstart
-ms.date: 01/31/2023
+ms.date: 02/03/2023
 #Customer intent: As a developer or cluster operator, I want to quickly create an AKS cluster and deploy an application so that I can see how to run applications using the managed Kubernetes service in Azure.
 ---
 
@@ -178,6 +178,11 @@ Use the following procedure to add the application definition:
     :::image type="content" source="./media/quick-kubernetes-deploy-bicep-extensibility-kubernetes-provider/bicep-extensibility-kubernetes-provider-import-kubernetes-manifest.png" alt-text="Screenshot of Visual Studio Code import Kubernetes Manifest":::
 
 1. In the prompt, select **azure-vote.yml**. This process creates an **azure-vote.bicep** in the same folder.
+1. At the end of **azure-vote.bicep**, add the following line to output the load balancer public IP.
+
+    ```bicep
+    output frontendIp string = coreService_azureVoteFront.status.loadBalancer.ingress[0].ip
+    ```
 
 1. Before the `output` statement in **main.bicep**, add the following Bicep to reference the newly created **azure-vote.bicep** module:
 
@@ -190,6 +195,14 @@ Use the following procedure to add the application definition:
     }
     ```
 
+1. At the end of **main.bicep**, add the following line to output the load balancer public IP:
+
+    ```bicep
+    output lbPublicIp string = kubernetes.outputs.frontendIp
+    ```
+
+1. Save both **main.bicep** and **azure-vote.bicep**.
+
 ## Deploy the Bicep file
 
 1. Deploy the Bicep file using either Azure CLI or Azure PowerShell.
@@ -219,94 +232,24 @@ Use the following procedure to add the application definition:
 
     It takes a few minutes to create the AKS cluster. Wait for the cluster to be successfully deployed before you move on to the next step.
 
-## Validate the Bicep deployment
-
-### Connect to the cluster
-
-To manage a Kubernetes cluster, use the Kubernetes command-line client, [kubectl][kubectl]. `kubectl` is already installed if you use Azure Cloud Shell.
-
-### [Azure CLI](#tab/azure-cli)
-
-1. Install `kubectl` locally using the [az aks install-cli][az-aks-install-cli] command:
-
-    ```azurecli
-    az aks install-cli
-    ```
-
-2. Configure `kubectl` to connect to your Kubernetes cluster using the [az aks get-credentials][az-aks-get-credentials] command. This command downloads credentials and configures the Kubernetes CLI to use them.
-
-    ```azurecli-interactive
-    az aks get-credentials --resource-group myResourceGroup --name myAKSCluster
-    ```
-
-3. Verify the connection to your cluster using the [kubectl get][kubectl-get] command. This command returns a list of the cluster nodes.
-
-    ```console
-    kubectl get nodes
-    ```
-
-    The following output example shows the three nodes created in the previous steps. Make sure the node status is *Ready*:
-
-    ```output
-    NAME                       STATUS   ROLES   AGE     VERSION
-    aks-agentpool-41324942-0   Ready    agent   6m44s   v1.12.6
-    aks-agentpool-41324942-1   Ready    agent   6m46s   v1.12.6
-    aks-agentpool-41324942-2   Ready    agent   6m45s   v1.12.6
-    ```
-
-### [Azure PowerShell](#tab/azure-powershell)
-
-1. Install `kubectl` locally using the [Install-AzAksKubectl][install-azakskubectl] cmdlet:
-
-    ```azurepowershell
-    Install-AzAksKubectl
-    ```
-
-2. Configure `kubectl` to connect to your Kubernetes cluster using the [Import-AzAksCredential][import-azakscredential] cmdlet. The following cmdlet downloads credentials and configures the Kubernetes CLI to use them.
+2. From the deployment output, look for the **outputs** section. For example:
 
-    ```azurepowershell-interactive
-    Import-AzAksCredential -ResourceGroupName myResourceGroup -Name myAKSCluster
-    ```
-
-3. Verify the connection to your cluster using the [kubectl get][kubectl-get] command. This command returns a list of the cluster nodes.
-
-    ```azurepowershell-interactive
-    kubectl get nodes
-    ```
-
-    The following output example shows the three nodes created in the previous steps. Make sure the node status is *Ready*:
-
-    ```plaintext
-    NAME                       STATUS   ROLES   AGE     VERSION
-    aks-agentpool-41324942-0   Ready    agent   6m44s   v1.12.6
-    aks-agentpool-41324942-1   Ready    agent   6m46s   v1.12.6
-    aks-agentpool-41324942-2   Ready    agent   6m45s   v1.12.6
+    ```bicep
+    "outputs": {
+      "controlPlaneFQDN": {
+        "type": "String",
+        "value": "myaks0201-d34ae860.hcp.eastus.azmk8s.io"
+      },
+      "lbPublicIp": {
+        "type": "String",
+        "value": "52.179.23.131"
+      }
+    },
     ```
 
----
-
-### Test the application
-
-When the application runs, a Kubernetes service exposes the application front end to the internet. This process can take a few minutes to complete.
-
-Monitor progress using the [kubectl get service][kubectl-get] command with the `--watch` argument.
-
-```console
-kubectl get service azure-vote-front --watch
-```
+    Make a note of the value of lbPublicIp.
 
-The **EXTERNAL-IP** output for the `azure-vote-front` service will initially show as *pending*.
-
-```output
-NAME               TYPE           CLUSTER-IP   EXTERNAL-IP   PORT(S)        AGE
-azure-vote-front   LoadBalancer   10.0.37.27   <pending>     80:30572/TCP   6s
-```
-
-Once the **EXTERNAL-IP** address changes from *pending* to an actual public IP address, use `CTRL-C` to stop the `kubectl` watch process. The following example output shows a valid public IP address assigned to the service:
-
-```output
-azure-vote-front   LoadBalancer   10.0.37.27   52.179.23.131   80:30572/TCP   2m
-```
+## Validate the Bicep deployment
 
 To see the Azure Vote app in action, open a web browser to the external IP address of your service.
 

articles/azure-resource-manager/bicep/bicep-extensibility-kubernetes-provider.md

@@ -2,7 +2,7 @@
 title: Bicep extensibility Kubernetes provider
 description: Learn how to Bicep Kubernetes provider  to deploy .NET applications to Azure Kubernetes Service clusters.
 ms.topic: conceptual
-ms.date: 02/01/2023
+ms.date: 02/03/2023
 ---
 
 # Bicep extensibility Kubernetes provider (Preview)
@@ -13,152 +13,50 @@ Learn how to Bicep extensibility Kubernetes provider to deploy .NET applications
 
 This preview feature can be enabled by configuring the [bicepconfig.json](./bicep-config.md):
 
-```bicep
+```json
 {
   "experimentalFeaturesEnabled": {
     "extensibility": true,
   }
 }
 ```
 
-## Import schema for Kubernetes provider
+## Import Kubernetes provider
+
+Deployments of Kubernetes must be contained within a [Bicep module file](./modules.md). To import the Kubernetes provider, use the [import statement](./bicep-import-providers.md). After importing the provider, you can refactor the Bicep module file as usual, such as by using variables and parameters. The Kubernetes manifest in YML does not include any programmability support by contract.
 
-Use the following syntax to import schema for Kubernetes provider:
+The following sample imports the Kubernetes provider:
 
 ```bicep
-resource aks 'Microsoft.ContainerService/managedClusters@2022-05-02-preview' existing = {
-  name: clusterName
-}
+@secure()
+param kubeConfig string
 
 import '[email protected]' with {
   namespace: 'default'
-  kubeConfig: aks.listClusterAdminCredential().kubeconfigs[0].value
+  kubeConfig: kubeConfig
 }
 ```
 
-The AKS cluster can be a new resource or an existing resource. The [Import Kubernetes manifest command](./visual-studio-code.md#bicep-commands) from Visual Studio Code can automatically add the code snippet automatically.
-
-## Define Kubernetes deployments and services
-
-*** Do I need to cover how a Kubernetes YML is transformed into Bicep?
-
-```yml
-apiVersion: apps/v1
-kind: Deployment
-metadata:
-  name: azure-vote-back
-spec:
-  replicas: 1
-  selector:
-    matchLabels:
-      app: azure-vote-back
-  template:
-    metadata:
-      labels:
-        app: azure-vote-back
-    spec:
-      nodeSelector:
-        "kubernetes.io/os": linux
-      containers:
-      - name: azure-vote-back
-        image: mcr.microsoft.com/oss/bitnami/redis:6.0.8
-        env:
-        - name: ALLOW_EMPTY_PASSWORD
-          value: "yes"
-        resources:
-          requests:
-            cpu: 100m
-            memory: 128Mi
-          limits:
-            cpu: 250m
-            memory: 256Mi
-        ports:
-        - containerPort: 6379
-          name: redis
----
-apiVersion: v1
-kind: Service
-metadata:
-  name: azure-vote-back
-spec:
-  ports:
-  - port: 6379
-  selector:
-    app: azure-vote-back
-```
+- **namespace**: Specify the namespace of the provider.
+- **KubeConfig**: Specify a base64 encoded value of the [Kubernetes cluster admin credentials](/rest/api/aks/managed-clusters/list-cluster-admin-credentials).
+
+The following sample shows how to pass `kubeConfig` value from parent Bicep file:
 
 ```bicep
-resource appsDeployment_azureVoteBack 'apps/Deployment@v1' = {
-  metadata: {
-    name: 'azure-vote-back'
-  }
-  spec: {
-    replicas: 1
-    selector: {
-      matchLabels: {
-        app: 'azure-vote-back'
-      }
-    }
-    template: {
-      metadata: {
-        labels: {
-          app: 'azure-vote-back'
-        }
-      }
-      spec: {
-        nodeSelector: {
-          'kubernetes.io/os': 'linux'
-        }
-        containers: [
-          {
-            name: 'azure-vote-back'
-            image: 'mcr.microsoft.com/oss/bitnami/redis:6.0.8'
-            env: [
-              {
-                name: 'ALLOW_EMPTY_PASSWORD'
-                value: 'yes'
-              }
-            ]
-            resources: {
-              requests: {
-                cpu: '100m'
-                memory: '128Mi'
-              }
-              limits: {
-                cpu: '250m'
-                memory: '256Mi'
-              }
-            }
-            ports: [
-              {
-                containerPort: 6379
-                name: 'redis'
-              }
-            ]
-          }
-        ]
-      }
-    }
-  }
+resource aks 'Microsoft.ContainerService/managedClusters@2022-05-02-preview' existing = {
+  name: 'demoAKSCluster'
 }
 
-resource coreService_azureVoteBack 'core/Service@v1' = {
-  metadata: {
-    name: 'azure-vote-back'
-  }
-  spec: {
-    ports: [
-      {
-        port: 6379
-      }
-    ]
-    selector: {
-      app: 'azure-vote-back'
-    }
+module kubernetes './kubernetes.bicep' = {
+  name: 'buildbicep-deploy'
+  params: {
+    kubeConfig: aks.listClusterAdminCredential().kubeconfigs[0].value
   }
 }
 ```
 
+The AKS cluster can be a new resource or an existing resource. The [Import Kubernetes manifest command](./visual-studio-code.md#bicep-commands) from Visual Studio Code can automatically add the import snippet automatically.
+
 ## Visual Studio Code import
 
 From Visual Studio Code, you can import Kubernetes manifest files to create Bicep module files. For more information, see [Visual Studio Code](./visual-studio-code.md#bicep-commands)

articles/azure-resource-manager/bicep/bicep-import-providers.md

@@ -0,0 +1,27 @@
+---
+title: Import Bicep extensibility providers
+description: Describes how to import Bicep extensibility providers.
+ms.topic: conceptual
+ms.date: 02/03/2023
+---
+
+# Import Bicep extensibility providers
+
+This article describes the syntax you use to import Bicep extensibility providers.
+
+## Import providers
+
+The syntax for importing providers is:
+
+```bicep
+import '<provider-name>@<provider-version>' with {
+  <provider-properties>
+}
+```
+
+See [Bicep extensibility Kubernetes provider](./bicep-extensibility-kubernetes-provider.md) for an example of using the Import statement.
+
+## Next steps
+
+- To learn about how to use the Kubernetes provider, see [Bicep extensibility Kubernetes provider](./bicep-extensibility-kubernetes-provider.md).
+- To go through a Kubernetes provider tutorial, see [Quickstart - Deploy Azure applications to Azure Kubernetes Services by using Bicep Kubernetes provider.](../../aks/learn/quick-kubernetes-deploy-bicep-extensibility-kubernetes-provider.md).