SquareOps Technologies Your DevOps Partner for Accelerating cloud journey.
This module provides a set of reusable, configurable, and scalable AWS EKS addons configurations. It enables users to easily deploy and manage a highly available EKS cluster using infrastructure as code. This module supports a wide range of features, including node termination handlers, VPC CNI add-ons, service monitors, Istio service meshes, Velero backups, and Karpenter provisioners. Users can configure these features using a set of customizable variables that allow for fine-grained control over the deployment. Additionally, this module is regularly updated to keep pace with the latest changes in the EKS ecosystem, ensuring that users always have access to the most up-to-date features and functionality.
module "eks-addons" {
source = "squareops/eks-addons/aws"
name = local.name
tags = local.additional_tags
vpc_id = "vpc-xxxxxx" # pass VPC ID
private_subnet_ids = ["subnet-xxxxx", "subnet-xxxxx"] # pass Subnet IDs
environment = local.environment
ipv6_enabled = local.ipv6_enabled
kms_key_arn = local.kms_key_arn
kms_policy_arn = "arn:aws:iam::xxx:policy/eks-kms-policy" # eks module will create kms_policy_arn
worker_iam_role_name = "update-eks-node-role" # enter role name created by eks module
worker_iam_role_arn = "arn:aws:iam::xxx:role/-eks-node-role" # enter roll ARN
eks_cluster_name = data.aws_eks_cluster.cluster.name
#VPC-CNI-DRIVER
amazon_eks_vpc_cni_enabled = false # enable VPC-CNI
#EBS-CSI-DRIVER
enable_amazon_eks_aws_ebs_csi_driver = false # enable EBS CSI Driver
amazon_eks_aws_ebs_csi_driver_config = {
values = [file("${path.module}/config/ebs-csi.yaml")]
}
## EBS-STORAGE-CLASS
single_az_ebs_gp3_storage_class_enabled = false # to enable ebs gp3 storage class
single_az_sc_config = [{ name = "infra-service-sc", zone = "${local.region}a" }]
## EfS-STORAGE-CLASS
efs_storage_class_enabled = false # to enable EBS storage class
## SERVICE-MONITORING-CRDs
service_monitor_crd_enabled = false # enable service monitor along with K8S-dashboard (required CRD) or when require service monitor in reloader and cert-manager
## METRIC-SERVER
metrics_server_enabled = false # to enable metrics server
metrics_server_helm_config = [file("${path.module}/config/metrics-server.yaml")]
vpa_config = {
values = [file("${path.module}/config/vpa-crd.yaml")]
}
## CLUSTER-AUTOSCALER
cluster_autoscaler_enabled = false # to enable cluster autoscaller
cluster_autoscaler_helm_config = [file("${path.module}/config/cluster-autoscaler.yaml")]
## NODE-TERMINATION-HANDLER
aws_node_termination_handler_enabled = false # to enable node termination handler
aws_node_termination_handler_helm_config = {
values = [file("${path.module}/config/aws-node-termination-handler.yaml")]
enable_service_monitor = false # to enable monitoring for node termination handler
}
## KEDA
keda_enabled = false # to enable Keda in the EKS cluster
keda_helm_config = {
values = [file("${path.module}/config/keda.yaml")]
}
## KARPENTER
karpenter_enabled = false # to enable Karpenter (installs required CRDs )
karpenter_helm_config = {
values = [file("${path.module}/config/karpenter.yaml")]
}
## KARPENTER-PROVISIONER
karpenter_provisioner_enabled = false # to enable provisioning nodes with Karpenter in the EKS cluster
karpenter_provisioner_config = {
provisioner_name = format("karpenter-provisioner-%s", local.name)
karpenter_label = ["Mgt-Services", "Monitor-Services", "ECK-Services"]
provisioner_values = file("./config/karpenter-management.yaml")
instance_capacity_type = ["spot"]
excluded_instance_type = ["nano", "micro", "small"]
ec2_instance_family = ["t3"]
ec2_instance_type = ["t3.medium"]
private_subnet_selector_key = "Environment"
private_subnet_selector_value = local.environment
security_group_selector_key = "aws:eks:cluster-name"
security_group_selector_value = "${local.environment}-${local.name}"
instance_hypervisor = ["nitro"]
kms_key_arn = local.kms_key_arn
}
## coreDNS-HPA (cluster-proportional-autoscaler)
coredns_hpa_enabled = false # to enable core-dns HPA
coredns_hpa_helm_config = {
values = [file("${path.module}/config/coredns-hpa.yaml")]
}
## EXTERNAL-SECRETS
external_secrets_enabled = false # to enable external secrets
external_secrets_helm_config = {
values = [file("${path.module}/config/external-secret.yaml")]
}
## CERT-MANAGER
cert_manager_enabled = false # to enable Cert-manager
cert_manager_helm_config = {
values = [file("${path.module}/config/cert-manager.yaml")]
enable_service_monitor = false # to enable monitoring for Cert Manager
cert_manager_letsencrypt_email = "email@email.com"
}
## CONFIG-RELOADER
reloader_enabled = false # to enable config reloader in the EKS cluster
reloader_helm_config = {
values = [file("${path.module}/config/reloader.yaml")]
enable_service_monitor = false # to enable monitoring for reloader
}
## INGRESS-NGINX
ingress_nginx_enabled = false # to enable ingress nginx
enable_private_nlb = false # to enable Internal (Private) Ingress , set this and ingress_nginx_enable "true" together
ingress_nginx_config = {
values = [file("${path.module}/config/ingress-nginx.yaml")]
enable_service_monitor = false # enable monitoring in nginx ingress
ingress_class_name = "nginx" # enter ingress class name according to your requirement (example: "nginx", "internal-ingress")
namespace = "nginx" # enter namespace according to the requirement (example: "ingress-nginx", "internal-ingress")
}
## AWS-APPLICATION-LOAD-BALANCER-CONTROLLER
aws_load_balancer_controller_enabled = true # to enable load balancer controller
aws_load_balancer_controller_helm_config = {
values = [file("${path.module}/config/aws-alb.yaml")]
}
## KUBERNETES-DASHBOARD
kubernetes_dashboard_enabled = false
k8s_dashboard_ingress_load_balancer = "nlb" ##Choose your load balancer type (e.g., NLB or ALB). Enable load balancer controller, if you require ALB, Enable Ingress Nginx if NLB.
alb_acm_certificate_arn = "arn:aws:acm:us-west-2:xxxxx:certificate/xxxxxxxx" # If using ALB in above parameter, ensure you provide the ACM certificate ARN for SSL.
k8s_dashboard_hostname = "dashboard-test.rnd.squareops.in" # Enter Hostname
# VELERO
velero_enabled = false # to enable velero
velero_notification_enabled = false # To enable slack notification for Velero
velero_config = {
namespaces = "" ## If you want full cluster backup, leave it blank else provide namespace.
slack_botToken = "xoxb-379541400966-iibMHnnoaPzVl"
slack_appToken = "xoxb-sgsehger-ddfnrndfnf"
slack_notification_channel_name = "slack-notification-channel"
retention_period_in_days = 45
schedule_backup_cron_time = "* 6 * * *"
velero_backup_name = "application-backup"
backup_bucket_name = "velero-test-eks-1.30" # Enter the S3 bucket name for velero
velero_values_yaml = [file("${path.module}/config/velero.yaml")]
}
## KUBECLARITY
kubeclarity_enabled = false # to enable kube clarity
kubeclarity_hostname = "kubeclarity.prod.in"
## KUBECOST
kubecost_enabled = false # to enable kube cost
kubecost_hostname = "kubecost.prod.in"
## DEFECT-DOJO
defectdojo_enabled = false # to enable defectdojo
defectdojo_hostname = "defectdojo.prod.in"
## FALCO
falco_enabled = false # to enable falco
slack_webhook = "xoxb-379541400966-iibMHnnoaPzVl"
# ISTIO
istio_enabled = false # to enable istio service mesh
istio_config = {
ingress_gateway_enabled = false
envoy_access_logs_enabled = false
prometheus_monitoring_enabled = false
istio_values_yaml = file("./config/istio.yaml")
}
}
| Release | Kubernetes 1.23 | Kubernetes 1.24 | Kubernetes 1.25 | Kubernetes 1.26 | Kubernetes 1.27 | Kubernetes 1.28 | Kubernetes 1.29 | Kubernetes 1.30 |
|---|---|---|---|---|---|---|---|---|
| Release 1.0.0 | ✔ | ✔ | ✔ | ✔ | ||||
| Release 1.1.0 | ✔ | ✔ | ✔ | ✔ | ||||
| Release 1.1.1 | ✔ | ✔ | ✔ | ✔ | ✔ | |||
| Release 1.1.2 | ✔ | ✔ | ✔ | ✔ | ✔ | |||
| Release 1.1.3 | ✔ | ✔ | ✔ | ✔ | ✔ | |||
| Release 1.1.4 | ✔ | ✔ | ✔ | ✔ | ✔ | |||
| Release 1.1.5 | ✔ | ✔ | ✔ | ✔ | ✔ | |||
| Release 1.1.6 | ✔ | ✔ | ✔ | ✔ | ✔ | |||
| Release 1.1.7 | ✔ | ✔ | ✔ | ✔ | ✔ | |||
| Release 1.1.8 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ||
| Release 3.0.0 | ❌ | ❌ | ❌ | ❌ | ❌ | ✔ | ✔ | ✔ |
Note: The latest release 3.0.0 support EKS version 1.28, 1.29 and 1.30. For EKS version <=1.27 refer the previous release.
The required IAM permissions to create resources from this module can be found here
Kubernetes addons are additional components that can be installed in a Kubernetes cluster to provide extra features and functionality. They are designed to work seamlessly with the Kubernetes API and can be managed just like any other Kubernetes resource. Some common examples of Kubernetes addons include:
AWS ALB
Amazon Web Services (AWS) Application Load Balancer (ALB) is a highly available and scalable load balancing service that routes incoming application traffic to multiple Amazon EC2 instances, containers, and IP addresses. It automatically distributes incoming application traffic across multiple targets, ensuring that your applications are highly available and scalable.With AWS ALB, you can handle increased traffic levels, automatically scale your applications, and improve the overall performance of your applications. ALB provides advanced routing capabilities, including content-based routing, host-based routing, and path-based routing, enabling you to route traffic to different target groups based on specific rules.
Node Termination Handler
In AWS, the Node termination handler can be used in Lambda functions or EC2 instances to handle the termination of the underlying instance or container. When an instance or container is terminated, the termination handler can be used to perform any necessary cleanup operations, such as closing open resources, before the instance or container is terminated. In an EC2 instance, the termination handler can be set by writing a script that runs on instance startup and sets the process.on('SIGTERM', callback) method. This script can be executed using a user data script or by adding it to the instance's startup script.EBS
Amazon Elastic Block Store (Amazon EBS) storage classes are different levels of performance and cost for Amazon EBS volumes. The storage classes determine the type of storage, performance characteristics, and cost of each Amazon EBS volume.There are currently four Amazon EBS storage classes:
Standard storage class: This is the default and most widely used storage class, offering a balance of low cost and high performance. It's suitable for a wide range of applications, including boot volumes, transactional databases, and big data workloads.
Provisioned IOPS (input/output operations per second) storage class: This class provides high-performance I/O for mission-critical and I/O-intensive workloads, such as large databases and I/O-bound applications.
Cold storage class: This class provides low-cost storage for infrequently accessed data, such as backups and archives. Cold storage is designed to deliver low cost and high durability.
Throughput Optimized HDD (hard disk drive) storage class: This class provides low-cost storage optimized for large, sequential workloads, such as big data and data warehouses.
Cert Manager
Cert Manager is a Kubernetes add-on that automates the management and issuance of TLS certificates from various issuing sources. It helps to eliminate manual steps in the certificate management process, provides cert renewals and integrates with other parts of the system.Cluster Autoscalar
Cluster Autoscaler is a Kubernetes component that automatically adjusts the number of nodes in a cluster based on the demand for resources. This allows you to optimize the cost of running your workloads while ensuring that they have the resources they need to run effectively. The Cluster Autoscaler works by monitoring the resource usage of your pods and comparing it to the available capacity on the nodes in the cluster. If there are pods that cannot be scheduled because of resource constraints, the Cluster Autoscaler will increase the number of nodes in the cluster until there is enough capacity to schedule the pending pods. Similarly, if there are nodes in the cluster that are underutilized, the Cluster Autoscaler can decrease the number of nodes to optimize resource utilization and reduce costs. Cluster Autoscaler is supported by many cloud providers, including Amazon Web Services (AWS), Google Cloud Platform (GCP), and Microsoft Azure. It can be easily integrated into your existing Kubernetes deployment and can be configured to use different scaling policies to meet the needs of your specific workloads.EFS
Amazon Elastic File System (Amazon EFS) is a fully managed, scalable, and highly available file storage service for use with Amazon Elastic Compute Cloud (Amazon EC2) instances. It provides a simple and scalable file storage solution that can be used by multiple EC2 instances at the same time, making it ideal for use cases such as big data, content management, and media sharing.Amazon EFS is easy to set up, manage, and scale, and it automatically replicates data across multiple Availability Zones for high durability and availability. The service is also highly performant, with low latency and high throughput, making it suitable for a wide range of workloads.
External Secrets
Kubernetes External Secrets is a feature in Kubernetes that allows secrets to be stored and managed outside of the cluster. External secrets are useful in scenarios where sensitive information, such as passwords or API keys, should not be stored directly in the cluster, but still needs to be used by applications running in the cluster. Kubernetes External Secrets can be stored in external systems such as Hashicorp Vault, AWS Secrets Manager, or GCP Secret Manager, and accessed by pods using a Kubernetes Secret object. The Secret object references the external secret and maps it to a Kubernetes Secret, which can then be used by pods in the same way as regular Kubernetes Secrets. By using External Secrets, organizations can ensure that sensitive information is securely managed and stored outside of the cluster, while still being able to use that information in their applications running in the cluster.Istio
Istio is an open-source service mesh platform that provides a set of tools for managing and securing microservices applications. Istio is designed to work with containerized applications and is built on top of Kubernetes, making it easy to deploy and manage. Some of the key features of Istio include: Traffic management: Istio provides the ability to control the flow of traffic between microservices, including load balancing, fault tolerance, and canary releases. Security: Istio provides built-in security features, such as mutual TLS authentication, for securing communication between microservices. Observability: Istio provides robust observability features, including distributed tracing, metric collection, and logging, making it easy to monitor and debug microservices applications. Configurable policies: Istio provides a flexible policy framework for controlling the behavior of microservices, allowing for easy enforcement of security, observability, and traffic management policies. Istio is widely adopted and has a strong ecosystem of partners and contributors, making it a popular choice for organizations looking to build and manage microservices applications. By using Istio, organizations can improve the reliability and security of their microservices applications and simplify the process of managing and operating them.Karpenter
Karpenter is a flexible, high-performance Kubernetes cluster autoscaler that helps improve application availability and cluster efficiency. Karpenter launches right-sized compute resources, (for example, Amazon EC2 instances), in response to changing application load in under a minute. Through integrating Kubernetes with AWS, Karpenter can provision just-in-time compute resources that precisely meet the requirements of your workload. Karpenter automatically provisions new compute resources based on the specific requirements of cluster workloads. These include compute, storage, acceleration, and scheduling requirements. Amazon EKS supports clusters using Karpenter, although Karpenter works with any conformant Kubernetes cluster.Karpenter-Provisioner
Karpernter Provisioner is a powerful provisioning module designed to streamline the deployment process for infrastructure as code (IaC) projects. It provides a set of intuitive and easy-to-use functions to automate the provisioning of resources on various cloud platforms.Metrics Server
Metric Server is a Kubernetes add-on that collects resource usage data from the Kubernetes API server and makes it available to other components, such as the Horizontal Pod Autoscaler (HPA) and the Cluster Autoscaler. The Metric Server collects data on the CPU and memory usage of pods and nodes in a cluster, and provides this data to other components in a format that they can use to make scaling decisions. The HPA, for example, can use the data provided by the Metric Server to automatically scale the number of replicas of a deployment based on the resource usage of the pods. The Cluster Autoscaler can also use this data to determine when to add or remove nodes from a cluster based on the resource utilization of the pods and nodes. Metric Server provides a simple and effective way to collect resource usage data from a cluster and make it available to other components for scaling and resource optimization. It is an important component for ensuring that your Kubernetes applications run effectively and efficiently in the cloud.Nginx Ingress Controller
Nginx Ingress Controller is a Kubernetes controller that manages external access to services running in a Kubernetes cluster. It provides load balancing, SSL termination, and name-based virtual hosting, among other features. The Nginx Ingress Controller works by using the Kubernetes API to dynamically configure an Nginx instance running outside of the cluster to route traffic to services within the cluster. This allows you to easily expose your services to external users and manage the routing of incoming traffic. The Nginx Ingress Controller provides a flexible and powerful way to manage incoming traffic to your Kubernetes applications. It is widely used in production environments and is well-suited for both simple and complex routing scenarios. Additionally, the Nginx Ingress Controller integrates with other Kubernetes components, such as the Kubernetes Ingress resource and cert-manager, to provide a complete solution for managing external access to your services.Reloader
Reloader can watch changes in ConfigMap and Secret and do rolling upgrades on Pods with their associated DeploymentConfigs, Deployments, Daemonsets, Statefulsets and Rollouts.Velero
Velero (previously known as Heptio Ark) is an open-source backup and disaster recovery solution for Kubernetes. Velero provides the ability to back up and restore Kubernetes cluster resources and persistent volumes, making it easy to recover from data loss or cluster failures. Some key features of Velero include: Cluster Backup and Restore: Velero allows users to create backups of their Kubernetes clusters and restore them to the same or different cluster. Persistent Volume Backup and Restore: Velero provides the ability to backup and restore persistent volumes, ensuring that data can be recovered even if the cluster fails. Incremental Backups: Velero supports incremental backups, which can be performed more frequently than full backups and reduce the amount of data transferred. Snapshot Integration: Velero integrates with cloud provider snapshot services, such as AWS EBS and GCE PD, to simplify the backup process and reduce the cost of storing backup data. Easy to Use CLI: Velero provides a user-friendly CLI that makes it easy to create, manage, and restore backups. Velero is designed to work with cloud native environments, making it a popular choice for organizations that run their applications in the cloud. By using Velero, organizations can improve the reliability and availability of their applications and ensure that they can recover from data loss or cluster failures.KubeClarity
KubeClarity helps you to secure your cloud-native applications and infrastructure by offering features such as automated threat detection, policy enforcement, compliance reporting, and continuous monitoring. It allows you to enforce security policies across all your Kubernetes environments and provides automated remediation of security issues, ensuring that your deployments are always secure and compliant.Kubecost
Kubecost provides real-time cost visibility and insights for teams using Kubernetes, helping you continuously reduce your cloud costs. Breakdown costs by any Kubernetes concepts, including deployment, service, namespace label, and more.DefectDojo
DefectDojo is an open-source application vulnerability management tool. It is designed to automate and streamline the process of managing application security testing efforts, including dynamic testing, static analysis, and manual penetration testing.Falcon
Falcon helps network administrators monitor malicious activities, apply mitigation techniques and block data tampering across multiple devices. Key feature:Endpoint Protection: Safeguards devices from malware, ransomware, and malicious activities.
Cloud-Native Architecture: Built for easy scalability with real-time threat detection in the cloud.
Behavioral Analysis: Identifies threats through behavioral analysis, not just known signatures.
Threat Intelligence: Integrates real-time threat intelligence feeds for up-to-date risk mitigation.
Incident Response: Enables swift investigation and remediation of security incidents.
Before enabling the Kubecost addon for your Amazon EKS cluster, please make sure to subscribe to the Kubecost - Amazon EKS cost monitoring license.
| Name | Version |
|---|---|
| terraform | >= 1.0.0 |
| aws | >= 4.23 |
| helm | >= 2.6 |
| kubernetes | >= 2.13 |
| random | >= 3.0.0 |
| time | >= 0.6.0 |
| Name | Version |
|---|---|
| aws | >= 4.23 |
| helm | >= 2.6 |
| kubernetes | >= 2.13 |
| random | >= 3.0.0 |
| time | >= 0.6.0 |
| Name | Source | Version |
|---|---|---|
| aws-ebs-csi-driver | ./modules/aws-ebs-csi-driver | n/a |
| aws-efs-csi-driver | ./modules/aws-efs-csi-driver | n/a |
| aws-efs-filesystem-with-storage-class | ./modules/aws-efs-filesystem-with-storage-class | n/a |
| aws-load-balancer-controller | ./modules/aws-load-balancer-controller | n/a |
| aws-node-termination-handler | ./modules/aws-node-termination-handler | n/a |
| aws_vpc_cni | ./modules/aws-vpc-cni | n/a |
| cert-manager | ./modules/cert-manager | n/a |
| cert-manager-le-http-issuer | ./modules/cert-manager-le-http-issuer | n/a |
| cluster-autoscaler | ./modules/cluster-autoscaler | n/a |
| coredns_hpa | ./modules/core-dns-hpa | n/a |
| external-secrets | ./modules/external-secret | n/a |
| ingress-nginx | ./modules/ingress-nginx | n/a |
| istio | ./modules/istio | n/a |
| karpenter | ./modules/karpenter | n/a |
| karpenter-provisioner | ./modules/karpenter-provisioner | n/a |
| keda | ./modules/keda | n/a |
| kubernetes-dashboard | ./modules/kubernetes-dashboard | n/a |
| metrics-server | ./modules/metrics-server | n/a |
| metrics-server-vpa | ./modules/metrics-server-vpa | n/a |
| reloader | ./modules/reloader | n/a |
| service-monitor-crd | ./modules/service-monitor-crd | n/a |
| single-az-sc | ./modules/aws-ebs-storage-class | n/a |
| velero | ./modules/velero | n/a |
| vpa-crds | ./modules/vpa-crds | n/a |
| Name | Type |
|---|---|
| aws_eks_addon.kubecost | resource |
| helm_release.defectdojo | resource |
| helm_release.falco | resource |
| helm_release.kubeclarity | resource |
| kubernetes_ingress_v1.kubecost | resource |
| kubernetes_namespace.defectdojo | resource |
| kubernetes_namespace.falco | resource |
| kubernetes_namespace.kube-clarity | resource |
| kubernetes_secret.kube-clarity | resource |
| kubernetes_secret.kubecost | resource |
| random_password.kube-clarity | resource |
| random_password.kubecost | resource |
| time_sleep.dataplane | resource |
| aws_caller_identity.current | data source |
| aws_eks_addon_version.kubecost | data source |
| aws_eks_cluster.eks | data source |
| aws_eks_cluster.eks_cluster | data source |
| aws_partition.current | data source |
| aws_region.current | data source |
| kubernetes_secret.defectdojo | data source |
| kubernetes_service.ingress-nginx | data source |
| kubernetes_service.istio-ingress | data source |
| Name | Description | Type | Default | Required |
|---|---|---|---|---|
| alb_acm_certificate_arn | ARN of the ACM certificate to be used for ALB Ingress. | string |
"" |
no |
| amazon_eks_aws_ebs_csi_driver_config | configMap for AWS EBS CSI Driver add-on | any |
{} |
no |
| amazon_eks_vpc_cni_enabled | Enable or disable the installation of the Amazon EKS VPC CNI addon. | bool |
false |
no |
| argocd_manage_add_ons | Enable managing add-on configuration via ArgoCD App of Apps | bool |
false |
no |
| auto_scaling_group_names | List of self-managed node groups autoscaling group names | list(string) |
[] |
no |
| aws_efs_csi_driver_helm_config | AWS EFS CSI driver Helm Chart config | any |
{} |
no |
| aws_load_balancer_controller_enabled | Enable or disable AWS Load Balancer Controller add-on for managing and controlling load balancers in Kubernetes. | bool |
false |
no |
| aws_load_balancer_controller_helm_config | Configuration for the AWS Load Balancer Controller Helm release | object({ |
{ |
no |
| aws_load_balancer_version | Specify the version of the AWS Load Balancer Controller for Ingress | string |
"1.4.4" |
no |
| aws_node_termination_handler_enabled | Enable or disable node termination handler | bool |
false |
no |
| aws_node_termination_handler_helm_config | AWS Node Termination Handler Helm Chart config | any |
{} |
no |
| aws_node_termination_handler_irsa_policies | Additional IAM policies for a IAM role for service accounts | list(string) |
[] |
no |
| cert_manager_domain_names | Domain names of the Route53 hosted zone to use with cert-manager | list(string) |
[] |
no |
| cert_manager_enabled | Enable or disable the cert manager add-on for EKS cluster. | bool |
false |
no |
| cert_manager_helm_config | Cert Manager Helm Chart config | any |
{} |
no |
| cert_manager_install_letsencrypt_r53_issuers | Enable or disable the creation of Route53 issuer while installing cert manager. | bool |
false |
no |
| cert_manager_irsa_policies | Additional IAM policies for a IAM role for service accounts | list(string) |
[] |
no |
| cert_manager_kubernetes_svc_image_pull_secrets | list(string) of kubernetes imagePullSecrets | list(string) |
[] |
no |
| cert_manager_letsencrypt_email | Specifies the email address to be used by cert-manager to request Let's Encrypt certificates | string |
"" |
no |
| cluster_autoscaler_chart_version | Version of the cluster autoscaler helm chart | string |
"9.29.0" |
no |
| cluster_autoscaler_enabled | Whether to enable the Cluster Autoscaler add-on or not. | bool |
false |
no |
| cluster_autoscaler_helm_config | CoreDNS Autoscaler Helm Chart config | any |
{} |
no |
| cluster_issuer | Specify the letsecrypt cluster-issuer for ingress tls. | string |
"letsencrypt-prod" |
no |
| coredns_hpa_enabled | Determines whether Horizontal Pod Autoscaling (HPA) for CoreDNS is enabled. | bool |
false |
no |
| coredns_hpa_helm_config | CoreDNS Autoscaler Helm Chart config | any |
{} |
no |
| custom_image_registry_uri | Custom image registry URI map of {region = dkr.endpoint } |
map(string) |
{} |
no |
| data_plane_wait_arn | Addon deployment will not proceed until this value is known. Set to node group/Fargate profile ARN to wait for data plane to be ready before provisioning addons | string |
"" |
no |
| defectdojo_enabled | Enable istio for service mesh. | bool |
false |
no |
| defectdojo_hostname | Specify the hostname for the kubecsot. | string |
"" |
no |
| efs_storage_class_enabled | Enable or disable the Amazon Elastic File System (EFS) add-on for EKS cluster. | bool |
false |
no |
| eks_cluster_endpoint | Endpoint for your Kubernetes API server | string |
null |
no |
| eks_cluster_name | Fetch Cluster ID of the cluster | string |
"" |
no |
| eks_cluster_version | The Kubernetes version for the cluster | string |
null |
no |
| eks_oidc_provider | The OpenID Connect identity provider (issuer URL without leading https://) |
string |
null |
no |
| enable_amazon_eks_aws_ebs_csi_driver | Enable EKS Managed AWS EBS CSI Driver add-on; enable_amazon_eks_aws_ebs_csi_driver and enable_self_managed_aws_ebs_csi_driver are mutually exclusive | bool |
false |
no |
| enable_ipv6 | Enable Ipv6 network. Attaches new VPC CNI policy to the IRSA role | bool |
false |
no |
| enable_private_nlb | Control wheather to install public nlb or private nlb. Default is private | bool |
false |
no |
| enable_self_managed_aws_ebs_csi_driver | Enable self-managed aws-ebs-csi-driver add-on; enable_self_managed_aws_ebs_csi_driver and enable_amazon_eks_aws_ebs_csi_driver are mutually exclusive | bool |
false |
no |
| environment | Environment identifier for the Amazon Elastic Kubernetes Service (EKS) cluster. | string |
"" |
no |
| external_secrets_enabled | Enable or disable External Secrets operator add-on for managing external secrets. | bool |
false |
no |
| external_secrets_helm_config | External Secrets operator Helm Chart config | any |
{} |
no |
| external_secrets_irsa_policies | Additional IAM policies for a IAM role for service accounts | list(string) |
[] |
no |
| external_secrets_secrets_manager_arns | List of Secrets Manager ARNs that contain secrets to mount using External Secrets | list(string) |
[ |
no |
| external_secrets_ssm_parameter_arns | List of Systems Manager Parameter ARNs that contain secrets to mount using External Secrets | list(string) |
[ |
no |
| falco_enabled | Determines whether Falco is enabled. | bool |
false |
no |
| ingress_nginx_config | Configure ingress-nginx to setup addons | object({ |
{ |
no |
| ingress_nginx_enabled | Control wheather to install public nlb or private nlb. Default is private | bool |
false |
no |
| ipv6_enabled | whether IPv6 enabled or not | bool |
false |
no |
| irsa_iam_permissions_boundary | IAM permissions boundary for IRSA roles | string |
"" |
no |
| irsa_iam_role_path | IAM role path for IRSA roles | string |
"/" |
no |
| istio_config | Configuration to provide settings for Istio | object({ |
{ |
no |
| istio_enabled | Enable istio for service mesh. | bool |
false |
no |
| k8s_dashboard_hostname | Specify the hostname for the k8s dashboard. | string |
"" |
no |
| k8s_dashboard_ingress_load_balancer | Controls whether to enable ALB Ingress or not. | string |
"nlb" |
no |
| karpenter_enabled | Enable or disable Karpenter, a Kubernetes-native, multi-tenant, and auto-scaling solution for containerized workloads on Kubernetes. | bool |
false |
no |
| karpenter_helm_config | Karpenter autoscaler add-on config | any |
{} |
no |
| karpenter_irsa_policies | Additional IAM policies for a IAM role for service accounts | list(string) |
[] |
no |
| karpenter_node_iam_instance_profile | Karpenter Node IAM Instance profile id | string |
"" |
no |
| karpenter_provisioner_config | Configuration to provide settings for Karpenter, including which private subnet to use, instance capacity types, and excluded instance types. | any |
{ |
no |
| karpenter_provisioner_enabled | Enable or disable the installation of Karpenter, which is a Kubernetes cluster autoscaler. | bool |
false |
no |
| keda_enabled | Enable or disable Kubernetes Event-driven Autoscaling (KEDA) add-on for autoscaling workloads. | bool |
false |
no |
| keda_helm_config | KEDA Event-based autoscaler add-on config | any |
{} |
no |
| keda_irsa_policies | Additional IAM policies for a IAM role for service accounts | list(string) |
[] |
no |
| kms_key_arn | ARN of the KMS key used to encrypt AWS resources in the EKS cluster. | string |
"" |
no |
| kms_policy_arn | Specify the ARN of KMS policy, for service accounts. | string |
"" |
no |
| kubeclarity_enabled | Enable or disable the deployment of an kubeclarity for Kubernetes. | bool |
false |
no |
| kubeclarity_hostname | Specify the hostname for the Kubeclarity. | string |
"" |
no |
| kubeclarity_namespace | Name of the Kubernetes namespace where the kubeclarity deployment will be deployed. | string |
"kubeclarity" |
no |
| kubecost_enabled | Enable or disable the deployment of an Kubecost for Kubernetes. | bool |
false |
no |
| kubecost_hostname | Specify the hostname for the kubecsot. | string |
"" |
no |
| kubernetes_dashboard_enabled | Determines whether k8s-dashboard is enabled or not | bool |
false |
no |
| metrics_server_enabled | Enable or disable the metrics server add-on for EKS cluster. | bool |
false |
no |
| metrics_server_helm_config | Metrics Server Helm Chart config | any |
{} |
no |
| metrics_server_helm_version | Version of the metrics server helm chart | string |
"3.11.0" |
no |
| name | Specify the name prefix of the EKS cluster resources. | string |
"" |
no |
| node_termination_handler_version | Specify the version of node termination handler | string |
"0.21.0" |
no |
| private_subnet_ids | Private subnets of the VPC which can be used by EFS | list(string) |
[ |
no |
| reloader_enabled | Enable or disable Reloader, a Kubernetes controller to watch changes in ConfigMap and Secret objects and trigger an application reload on their changes. | bool |
false |
no |
| reloader_helm_config | Reloader Helm Chart config | any |
{} |
no |
| self_managed_aws_ebs_csi_driver_helm_config | Self-managed aws-ebs-csi-driver Helm chart config | any |
{} |
no |
| service_monitor_crd_enabled | Enable or disable the installation of Custom Resource Definitions (CRDs) for Prometheus Service Monitor. | bool |
false |
no |
| single_az_ebs_gp3_storage_class_enabled | Whether to enable the Single AZ storage class or not. | bool |
false |
no |
| single_az_sc_config | Name and regions for storage class in Key-Value pair. | list(any) |
[] |
no |
| slack_webhook | The Slack webhook URL used for notifications. | string |
"" |
no |
| storage_class_name | Specify the hostname for the kubecsot. | string |
"infra-service-sc" |
no |
| tags | Additional tags (e.g. map('BusinessUnit,XYZ) |
map(string) |
{} |
no |
| velero_config | Configuration to provide settings for Velero, including which namespaces to backup, retention period, backup schedule, and backup bucket name. | any |
{ |
no |
| velero_enabled | Enable or disable the installation of Velero, which is a backup and restore solution for Kubernetes clusters. | bool |
false |
no |
| velero_notification_enabled | Enable or disable the notification for velero backup. | bool |
false |
no |
| vpa_config | Configure VPA CRD to setup addon | object({ |
{ |
no |
| vpc_id | ID of the VPC where the cluster and its nodes will be provisioned | string |
"" |
no |
| worker_iam_role_arn | Specify the IAM role Arn for the nodes | string |
"" |
no |
| worker_iam_role_name | Specify the IAM role for the nodes that will be provisioned through karpenter | string |
"" |
no |
| Name | Description |
|---|---|
| defectdojo | DefectDojo endpoint and credentials |
| ebs_encryption_enable | Whether Amazon Elastic Block Store (EBS) encryption is enabled or not. |
| efs_id | ID of the Amazon Elastic File System (EFS) that has been created for the EKS cluster. |
| environment | Environment Name for the EKS cluster |
| internal_nginx_ingress_controller_dns_hostname | DNS hostname of the NGINX Ingress Controller. |
| istio_ingressgateway_dns_hostname | DNS hostname of the Istio Ingress Gateway. |
| k8s_dashboard_admin_token | Kubernetes-Dashboard Admin Token |
| k8s_dashboard_read_only_token | Kubernetes-Dashboard Read Only Token |
| kubeclarity | Kubeclarity endpoint and credentials |
| kubecost | Kubecost endpoint and credentials |
| nginx_ingress_controller_dns_hostname | DNS hostname of the NGINX Ingress Controller. |
To report an issue with a project:
- Check the repository's issue tracker on GitHub
- Search to see if the issue has already been reported
- If you can't find an answer to your question in the documentation or issue tracker, you can ask a question by creating a new issue. Be sure to provide enough context and details so others can understand your problem.
- Contributing to the project can be a great way to get involved and get help. The maintainers and other contributors may be more likely to help you if you're already making contributions to the project.
Apache License, Version 2.0, January 2004 (http://www.apache.org/licenses/).
To support a GitHub project by liking it, you can follow these steps:
-
Visit the repository: Navigate to the GitHub repository.
-
Click the "Star" button On the repository page, you'll see a "Star" button in the upper right corner. Clicking on it will star the repository, indicating your support for the project.
-
Optionally, you can also leave a comment on the repository or open an issue to give feedback or suggest changes.
Starring a repository on GitHub is a simple way to show your support and appreciation for the project. It also helps to increase the visibility of the project and make it more discoverable to others.
We believe that the key to success in the digital age is the ability to deliver value quickly and reliably. That’s why we offer a comprehensive range of DevOps & Cloud services designed to help your organization optimize its systems & Processes for speed and agility.
- We are an AWS Advanced consulting partner which reflects our deep expertise in AWS Cloud and helping 100+ clients over the last 5 years.
- Expertise in Kubernetes and overall container solution helps companies expedite their journey by 10X.
- Infrastructure Automation is a key component to the success of our Clients and our Expertise helps deliver the same in the shortest time.
- DevSecOps as a service to implement security within the overall DevOps process and helping companies deploy securely and at speed.
- Platform engineering which supports scalable,Cost efficient infrastructure that supports rapid development, testing, and deployment.
- 24*7 SRE service to help you Monitor the state of your infrastructure and eradicate any issue within the SLA.
We provide support on all of our projects, no matter how small or large they may be.
You can find more information about our company on this squareops.com, follow us on Linkedin, or fill out a job application. If you have any questions or would like assistance with your cloud strategy and implementation, please don't hesitate to contact us.