more updates

Author: AbhishekMallick01

articles/backup/azure-kubernetes-service-backup-troubleshoot.md

@@ -14,9 +14,14 @@ This article provides troubleshooting steps that help you resolve Azure Kubernet
 
 ## AKS Backup Extension installation error resolutions
 
-### Error 1
+### Scenario 1
+
+**Error message**:
+
+   ```Erroe
+   {Helm installation from path [] for release [azure-aks-backup] failed with the following error: err [release azure-aks-backup failed, and has been uninstalled due to atomic being set: failed post-install: timed out waiting for the condition]} occurred while doing the operation: {Installing the extension} on the config"`
+   ```
 
-**Error message**: `{Helm installation from path [] for release [azure-aks-backup] failed with the following error: err [release azure-aks-backup failed, and has been uninstalled due to atomic being set: failed post-install: timed out waiting for the condition]} occurred while doing the operation: {Installing the extension} on the config"`
 
 **Cause**: The extension has been installed successfully, but the pods aren't spawning. This happens because the required compute and memory aren't available for the pods.
 
@@ -28,11 +33,15 @@ To scale node pool on Azure portal, follow these steps:
 1. Select **Scale node pool**, and then update the *minimum* and *maximum* values on the **Node count range**.
 1. Select **Apply**.
 
-### Error 2
+### Scenario 2
 
-Error message: `BackupStorageLocation "default" is unavailable: rpc error: code = Unknown desc = azure.BearerAuthorizer#WithAuthorization: Failed to refresh the Token for request to https://management.azure.com/subscriptions/e30af180-aa96-4d81-981a-b67570b0d615/resourceGroups/AzureBackupRG_westeurope_1/providers/Microsoft.Storage/storageAccounts/devhayyabackup/listKeys?%24expand=kerb&api-version=2019-06-01: StatusCode=404 -- Original Error: adal: Refresh request failed. Status Code = '404'. Response body: no azure identity found for request clientID 4e95##### REDACTED #####0777`
+**Error message**:
 
-`Endpoint http://169.254.169.254/metadata/identity/oauth2/token?api-version=2018-02-01&client_id=4e95dcc5-a769-4745-b2d9-`
+   ```Error
+   BackupStorageLocation "default" is unavailable: rpc error: code = Unknown desc = azure.BearerAuthorizer#WithAuthorization: Failed to refresh the Token for request to https://management.azure.com/subscriptions/e30af180-aa96-4d81-981a-b67570b0d615/resourceGroups/AzureBackupRG_westeurope_1/providers/Microsoft.Storage/storageAccounts/devhayyabackup/listKeys?%24expand=kerb&api-version=2019-06-01: StatusCode=404 -- Original Error: adal: Refresh request failed. Status Code = '404'. Response body: no azure identity found for request clientID 4e95##### REDACTED #####0777`
+
+   Endpoint http://169.254.169.254/metadata/identity/oauth2/token?api-version=2018-02-01&client_id=4e95dcc5-a769-4745-b2d9-
+   ```
 
 **Cause**: When you enable pod-managed identity on your AKS cluster, an *AzurePodIdentityException* named *aks-addon-exception* is added to the *kube-system* namespace. An *AzurePodIdentityException* allows pods with certain labels to access the Azure Instance Metadata Service (IMDS) endpoint without being intercepted by the NMI server.
 
@@ -42,20 +51,30 @@ The extension pods aren't exempt, and require the Azure Active Directory (Azure
 
 1. Run the following command:
 
-   `az aks pod-identity exception add --resource-group shracrg --cluster-name shractestcluster --namespace dataprotection-microsoft --pod-labels app.kubernetes.io/name=dataprotection-microsoft-kubernetes`
+
+   ```azurepowershell-interactive
+   az aks pod-identity exception add --resource-group shracrg --cluster-name shractestcluster --namespace dataprotection-microsoft --pod-labels app.kubernetes.io/name=dataprotection-microsoft-kubernetes
+   ```
 
 2. To verify *Azurepodidentityexceptions* in cluster, run the following command:
 
-   `kubectl get Azurepodidentityexceptions --all-namespaces`
+   ```azurepowershell-interactive
+   kubectl get Azurepodidentityexceptions --all-namespaces
+   ```
 
 3. To assign the *Storage Account Contributor* role to the extension identity, run the following command:
 
-   `az role assignment create --assignee-object-id $(az k8s-extension show --name azure-aks-backup --cluster-name aksclustername --resource-group aksclusterresourcegroup --cluster-type managedClusters --query aksAssignedIdentity.principalId --output tsv) --role 'Storage Account Contributor' --scope /subscriptions/subscriptionid/resourceGroups/storageaccountresourcegroup/providers/Microsoft.Storage/storageAccounts/storageaccountname`
+   ```azurepowershell-interactive
+   az role assignment create --assignee-object-id $(az k8s-extension show --name azure-aks-backup --cluster-name aksclustername --resource-group aksclusterresourcegroup --cluster-type managedClusters --query aksAssignedIdentity.principalId --output tsv) --role 'Storage Account Contributor' --scope /subscriptions/subscriptionid/resourceGroups/storageaccountresourcegroup/providers/Microsoft.Storage/storageAccounts/storageaccountname
+   ```
 
-### Error 3
+### Scenario 3
 
-**Error message**: `{"Message":"Error in the getting the Configurations: error {Post \https://centralus.dp.kubernetesconfiguration.azure.com/subscriptions/ subscriptionid /resourceGroups/ aksclusterresourcegroup /provider/managedclusters/clusters/ aksclustername /configurations/getPendingConfigs?api-version=2021-11-01\: dial tcp: lookup centralus.dp.kubernetesconfiguration.azure.com on 10.63.136.10:53: no such host}","LogType":"ConfigAgentTrace","LogLevel":"Error","Environment":"prod","Role":"ClusterConfigAgent","Location":"centralus","ArmId":"/subscriptions/ subscriptionid /resourceGroups/ aksclusterresourcegroup /providers/Microsoft.ContainerService/managedclusters/ aksclustername ","CorrelationId":"","AgentName":"ConfigAgent","AgentVersion":"1.8.14","AgentTimestamp":"2023/01/19 20:24:16"}`
+**Error message**:
 
+   ```Error
+   {"Message":"Error in the getting the Configurations: error {Post \https://centralus.dp.kubernetesconfiguration.azure.com/subscriptions/ subscriptionid /resourceGroups/ aksclusterresourcegroup /provider/managedclusters/clusters/ aksclustername /configurations/getPendingConfigs?api-version=2021-11-01\: dial tcp: lookup centralus.dp.kubernetesconfiguration.azure.com on 10.63.136.10:53: no such host}","LogType":"ConfigAgentTrace","LogLevel":"Error","Environment":"prod","Role":"ClusterConfigAgent","Location":"centralus","ArmId":"/subscriptions/ subscriptionid /resourceGroups/ aksclusterresourcegroup /providers/Microsoft.ContainerService/managedclusters/ aksclustername ","CorrelationId":"","AgentName":"ConfigAgent","AgentVersion":"1.8.14","AgentTimestamp":"2023/01/19 20:24:16"}`
+   ```
 **Cause**: Specific FQDN/application rules are required to use cluster extensions in the AKS clusters. [Learn more](/azure/aks/limit-egress-traffic#cluster-extensions).
 
 This error appears due to absence of these FQDN rules because of which configuration information from the Cluster Extensions service wasn't available.
@@ -64,23 +83,33 @@ This error appears due to absence of these FQDN rules because of which configura
 
 1. To fetch *Existing CoreDNS-custom* YAML in your cluster (save it on your local for reference later), run the following command:
 
-   `kubectl get configmap coredns-custom -n kube-system -o yaml`
+   ```azurepowershell-interactive
+   kubectl get configmap coredns-custom -n kube-system -o yaml
+   ```
 
 2. To override mapping for *Central US DP* endpoint to public IP (download the YAML file attached), run the following command:
 
-   `kubectl apply -f corednsms.yaml`
+   ```azurepowershell-interactive
+   kubectl apply -f corednsms.yaml
+   ```
 
 3. To force reload `coredns` pods, run the following command:
 
-   `kubectl delete pod --namespace kube-system -l k8s-app=kube-dns`
+   ```azurepowershell-interactive
+   kubectl delete pod --namespace kube-system -l k8s-app=kube-dns
+   ```
 
 4. To perform `NSlookup` from the *ExtensionAgent* pod to check if *coreDNS-custom* is working, run the following command:
 
-   `kubectl exec -i -t pod/extension-agent-<pod guid that's there in your cluster> -n kube-system -- nslookup centralus.dp.kubernetesconfiguration.azure.com`
+   ```azurepowershell-interactive
+   kubectl exec -i -t pod/extension-agent-<pod guid that's there in your cluster> -n kube-system -- nslookup centralus.dp.kubernetesconfiguration.azure.com
+   ```
 
 5. To check logs of the *ExtensionAgent* pod, run the following command:
 
-   `kubectl logs pod/extension-agent-<pod guid that’s there in your cluster> -n kube-system --tail=200`
+   ```azurepowershell-interactive
+   kubectl logs pod/extension-agent-<pod guid that’s there in your cluster> -n kube-system --tail=200
+   ```
 
 6. Delete and reinstall Backup Extension to initiate backup.