Closed foxnix closed 3 years ago
This may be affecting other Generation 2 SKU's as well.
š
Trying this now against the latest master
branch (which has had no changes to AKS since the last release) - it appears this works:
$ cat main.tf
provider "azurerm" {
features {}
}
resource "azurerm_resource_group" "example" {
name = "tomdevaksrg"
location = "West Europe"
}
resource "azurerm_kubernetes_cluster" "example" {
name = "tomdevaks"
location = azurerm_resource_group.example.location
resource_group_name = azurerm_resource_group.example.name
dns_prefix = "tomdevaks"
default_node_pool {
name = "default"
node_count = 1
vm_size = "Standard_DC2s_v2"
}
identity {
type = "SystemAssigned"
}
tags = {
Environment = "Production"
}
}
Which ends up getting deployed with Kubernetes version 1.18.14
- as such I believe this issue (which appears to be an upstream issue) is now resolved. If you're still experiencing this issue then please ensure you're running the latest version of the Azure Provider (v2.48.0 at the time of writing) and we'll take another look.
Thanks!
I'm going to lock this issue because it has been closed for 30 days ā³. This helps our maintainers find and focus on the active issues.
If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error š¤ š , please reach out to my human friends š hashibot-feedback@hashicorp.com. Thanks!
Community Note
Terraform (and AzureRM Provider) Version
Affected Resource(s)
azurerm_kubernetes_cluster
Terraform Configuration Files
Crash Output
Expected Behaviour
Create a nodepool with DC2s_v2 (Gen2s) VMs.
Actual Behaviour
Error above.
Steps to Reproduce
Deploy an
azurerm_kubernetes_cluster
resource with same configuration, important section:Important Factoids
Nothing special.