-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable API Server VNET Integration #26
base: main
Are you sure you want to change the base?
Conversation
e33c18b
to
4aaba8c
Compare
looks like it is failing because of this
|
This is possible, noting it is a preview service: resource "azapi_update_resource" "aks_api_server_access_profile" {
type = "Microsoft.ContainerService/managedClusters@2024-09-02-preview"
body = {
properties = {
apiServerAccessProfile = {
enableVnetIntegration = var.api_server_vnet_integration #true
}
}
}
resource_id = azurerm_kubernetes_cluster.this.id
} & because it is in preview the variable needs decorating like this to align to AVM spec requirements (& confirmation from the PG, I believe) : variable "api_server_vnet_integration" {
type = bool
default = false
description = <<DESCRIPTION
# https://azure.github.io/Azure-Verified-Modules/specs/shared/#id-sfr1---category-composition---preview-services
THIS IS A VARIABLE USED FOR A PREVIEW SERVICE/FEATURE, MICROSOFT MAY NOT PROVIDE SUPPORT FOR THIS, PLEASE CHECK THE PRODUCT DOCS FOR CLARIFICATION
Enable VNET integration for the AKS cluster
This requires the following preview feature registered on the subscription:
az feature register --namespace "Microsoft.ContainerService" --name "EnableAPIServerVnetIntegrationPreview"
DESCRIPTION
} |
@kewalaka the problem is that the subscription where our CI is running does not have preview features registered. |
https://learn.microsoft.com/en-us/azure/aks/api-server-vnet-integration
closes #13