From df7d7c73acdbc15d028ebe41a8f2d8ed8732b317 Mon Sep 17 00:00:00 2001 From: philthynz Date: Wed, 26 May 2021 13:12:12 +1200 Subject: [PATCH] Add note to avoid conflicts when enabling AGIC (#11954) --- website/docs/r/kubernetes_cluster.html.markdown | 2 ++ 1 file changed, 2 insertions(+) diff --git a/website/docs/r/kubernetes_cluster.html.markdown b/website/docs/r/kubernetes_cluster.html.markdown index 0a8375352606..fae5cef2d728 100644 --- a/website/docs/r/kubernetes_cluster.html.markdown +++ b/website/docs/r/kubernetes_cluster.html.markdown @@ -456,6 +456,8 @@ An `ingress_application_gateway` block supports the following: * `subnet_id` - (Optional) The ID of the subnet on which to create an Application Gateway, which in turn will be integrated with the ingress controller of this Kubernetes Cluster. See [this](https://docs.microsoft.com/en-us/azure/application-gateway/tutorial-ingress-controller-add-on-new) page for further details. +-> **NOTE** If using `enabled` in conjunction with `only_critical_addons_enabled`, the AGIC pod will fail to start. A seperate `azurerm_kubernetes_cluster_node_pool` is required to run the AGIC pod successfully. This is because AGIC is classed as a "non-critical addon". + --- A `role_based_access_control` block supports the following: