Open zioproto opened 1 year ago
Any chance of this possibly getting this reprioritized and reclassified?
I am trying to create a cluster that is entirely within our private network and would love to make use of this feature. Right now trying to set the subnet results in the following error:
I would argue that this is actually a bug in the current version of the module as the module allows setting a subnet here: (https://github.com/Azure/terraform-azurerm-aks/blob/main/main.tf#L262)
I think instead of adding a new variable, it would be better to simply set this to true if the subnet is set.
@lonegunmanb @zioproto would it be possible to reclassify as a bug and make the suggested change?
local environment information: Terraform v1.8.5 on windows_amd64
@richshadman I am hitting the same problem now, though my problem is because of KMS keyvault network access being set to Private. I'm pretty sure a week or so ago when I last deployed the cluster with the same settings the Azure API didn't enforce the vnet integration requirement, but it certainly does now.
Anyway, I would really like to have this switch available and it looks like the @bislydev commit above would add it?
@richshadman you are right. I identified a mistake on our side, we merged the var.api_server_subnet_id
variable that is actually part of the preview feature API Server VNET Intergration, in PR https://github.com/Azure/terraform-azurerm-aks/pull/381
Please bare with us until the feature is declared as GA. Then me and @lonegunmanb will update this module as soon as possible.
Any info when will it be GA?
@richshadman @lonegunmanb @zioproto When this will be in GA? Please help.
Is there an existing issue for this?
Description
AKS API Server VNet Integration. The product is still in preview but let's track it in a GitHub issue so we are ready to merge a PR as soon is promoted to GA.
Resources:
Status:
New or Affected Resource(s)/Data Source(s)
azurerm_kubernetes_cluster
Potential Terraform Configuration
References
No response