edits for the billing model

Author: tejaswikolli-web

articles/marketplace/azure-container-technical-assets-kubernetes.md

@@ -204,10 +204,25 @@ Ensure the Helm chart adheres to the following rules:
 
     :::image type="content" source="./media/azure-container/billing-identifier.png" alt-text="A screenshot of a properly formatted values.yaml file is shown. The images are using digests. The content resembles the sample values.yaml file linked in this article.":::
 
+### Available billing models
+
+Billing model  |Definition  
+---------------|-----------
+Per core|Usage is charged for every core used by the Kubernetes application’s extension instance (reported at hourly frequency)
+Per every core in cluster|Usage is charged based on total number of cores in the kubernetes cluster (reported at hourly frequency
+Per cluster|Usage is charged for each instance of the Kubernetes application extension on the cluster (reported at hourly frequency)
+Per every node in cluster|Usage is charged based on total number of nodes in the cluster (reported at hourly frequency)
+Per node|Usage is charged for each node on which the Kubernetes application’s extension instance runs on (reported at hourly frequency)
+Per pod|Usage is charged for each pod on which the Kubernetes application’s extension instance runs (reported at hourly frequency)
+Bring your own licensing (BYOL)|Usage is charged based on existing licensing that the customer can bring in.
+
+
 ### Make updates based on your billing model
 
 After reviewing the billing models available, select one appropriate for your use case and complete the following steps:
 
+Follow steps to add identifier in the *Per core* billing model:
+
 - Add a billing identifier label and cpu cores request to your `deployment.yaml` file.
 
     :::image type="content" source="./media/azure-container/billing-identifier-label.png" alt-text="A screenshot of a properly formatted billing identifier label in a deployment.yaml file. The content resembles the sample depoyment.yaml file linked in this article":::
@@ -218,6 +233,10 @@ After reviewing the billing models available, select one appropriate for your us
 
     :::image type="content" source="./media/azure-container/billing-identifier-value.png" alt-text="A screenshot of a properly formatted values.yaml file, showing the global > azure > billingIdentifier field.":::
 
+Follow steps to add a billing identifier label in the *Per core* billing model:
+
+- Add a billing identifier label `azure-extensions-usage-release-identifier` to your `deployment.yaml` file (Under **Template** > **Metadata** > **Labels**>).
+
 Note that at deployment time, the cluster extensions feature will replace the billing identifier value with the extension type name you provide while setting up plan details.
 
 For examples configured to deploy the [Azure Voting App][azure-voting-app], see the following: