Use cluster api from variable instead of data source

SCT-Engineering · Sep 6, 2024 · 7be7252 · 7be7252
1 parent c3fb00d
commit 7be7252
Show file tree

Hide file tree

Showing 2 changed files with 13 additions and 6 deletions.
diff --git a/main.tf b/main.tf
@@ -55,11 +55,11 @@ resource "kubernetes_namespace" "ns" {
   }
 }
 
-data "kubernetes_service" "apiserver" {
-  metadata {
-    name = "kubernetes"
-  }
-}
+# data "kubernetes_service" "apiserver" {
+#   metadata {
+#     name = "kubernetes"
+#   }
+# }
 
 resource "helm_release" "base" {
   depends_on = [module.images]
@@ -110,7 +110,8 @@ resource "helm_release" "istiod" {
   }
   set {
     name  = "globalproxy.excludeIPRanges"
-    value = "${data.kubernetes_service.apiserver.spec[0].cluster_ip}/32"
+    value = "${var.kubernetes_service_apiserver}/32"
+    # value = "${data.kubernetes_service.apiserver.spec[0].cluster_ip}/32"
   }
 }
 

diff --git a/variables.tf b/variables.tf
@@ -62,3 +62,9 @@ variable "enable_egress_gateway" {
   type        = bool
   default     = true
 }
+
+variable "kubernetes_service_apiserver" {
+  description = "Use to exclude internal API service traffic from the service mesh; it should not change but could be necessary to lookup"
+  type        = string
+  default     = "172.20.0.1"
+}