You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am writing to raise some queries regarding our current usage of Azure CAF (Cloud Adoption Framework) modules, particularly in light of recent API issues we have encountered while trying to connect AKS kubernetes cluster via pipeline.
We have been experiencing difficulties with connecting to AKS cluster and upon investigation, we have identified that we have not specified any default API to connect the cluster.
Error:
Error : retrieving Cluster: (Managed Cluster Name : XXXXXXXXX / resource Group "xxxxxxxxxx"): containerservice.ManagedClusterClient#Get: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned error. Status=400 Code: "NoRegisteredProviderFound" Message="No registered resource provider found for location 'uksouth' and API version '2022-01-02-preview' for tyoe 'managedClusters'.
Currently, we are using a specific version of Azurerm 2.99
Could you kindly provide some insights or guidance on the following questions:
Will upgrading Azurerm to the latest version potentially resolve API issues (connecting with new available API) we are encountering?
Are there any compatibility considerations or risks associated with upgrading to the latest Azurerm version?
How should we proceed with testing and implementation to ensure a smooth transition and minimal disruption to our operations?
The text was updated successfully, but these errors were encountered:
Hello Team,
I am writing to raise some queries regarding our current usage of Azure CAF (Cloud Adoption Framework) modules, particularly in light of recent API issues we have encountered while trying to connect AKS kubernetes cluster via pipeline.
We have been experiencing difficulties with connecting to AKS cluster and upon investigation, we have identified that we have not specified any default API to connect the cluster.
Error:
Error : retrieving Cluster: (Managed Cluster Name : XXXXXXXXX / resource Group "xxxxxxxxxx"): containerservice.ManagedClusterClient#Get: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned error. Status=400 Code: "NoRegisteredProviderFound" Message="No registered resource provider found for location 'uksouth' and API version '2022-01-02-preview' for tyoe 'managedClusters'.
Currently, we are using a specific version of Azurerm 2.99
Could you kindly provide some insights or guidance on the following questions:
Will upgrading Azurerm to the latest version potentially resolve API issues (connecting with new available API) we are encountering?
Are there any compatibility considerations or risks associated with upgrading to the latest Azurerm version?
How should we proceed with testing and implementation to ensure a smooth transition and minimal disruption to our operations?
The text was updated successfully, but these errors were encountered: