add ingress to monitoring services

Author: Friz-zy

README.md

@@ -41,7 +41,9 @@ Helm upgrade `reset_values` flag set to `true` for everything except databases l
 |cluster_endpoint|Endpoint for your Kubernetes API server|
 |cluster_certificate_authority_data|Base64 encoded certificate data required to communicate with the cluster|
 
-Also `~/.kube/eks-${data.aws_region.current"}-${module.eks.cluster_name}` will be created by `aws eks` utility.
+Also `~/.kube/eks-${account_id}-${region}-${cluster_name}` will be created by `aws eks` utility.
+
+You can describe apisix ingress external address with kubectl: `kubectl get service/apisix-ingress-controller-apisix-gateway -n ingress-apisix`.
 
 ## About the Author
 

example/main.tf

@@ -3,8 +3,10 @@ provider "aws" {
 }
 
 locals {
-  cluster_name = "test"
-  admin_email  = "[email protected]"
+  cluster_name        = "test"
+  admin_email         = "[email protected]"
+  ingress_domain      = "cluster.local"
+  cert_manager_issuer = ""
 
   vpc_name = "eks_${local.cluster_name}"
   azs = data.aws_availability_zones.available.names
@@ -128,6 +130,8 @@ module "eks" {
 
   cluster_name                                    = local.cluster_name
   admin_email                                     = local.admin_email
+  ingress_domain                                  = local.ingress_domain
+  cert_manager_issuer                             = local.cert_manager_issuer
   vpc_id                                          = module.vpc.vpc_id
   number_of_multi_az                              = local.number_of_multi_az
   self_managed_node_group_number_of_multi_az      = local.self_managed_node_group_number_of_multi_az