EKS Auto Mode Arrives in Terraform – Simplify Kubernetes Today

During AWS re:Invent 2024 AWS released a new feature to EKS i.e EKS Auto Mode, which .

I will also talk about the differences in the terraform code which we used for eks cluster before Auto mode feature v/s the terraform code after using using Auto mode feature and how it save a beginner who does not know anything EKS.

Motivation

• Terraform provider for AWS released a new version
  
  
  
  
  
  • Terraform eks module released a new version
    
    
    

    
    
    
    Let's use Terraform AWS EKS module for EKS Auto Mode
    

    
    
    

    
    

    If you want to follow along use this

    
    
    

    
    
    • One node pool (general purpose) created by EKS Auto mode
    
    

    
    
    
    
    

    
    

    • There are no nodes or pods in the cluster( no workload is running) or can also say I did not provisioned any nodes so far because that the job of EKS Auto mode now.

    
    

    • The moment I install a sample using this
      
      

      
      
      
      
      

      CODE Kopieren

       kubectl get po
      
      NAME                    READY   STATUS    RESTARTS   AGE
      
      test-65b7dbddd4-j6mbt   1/1     Running   0          104s
      
      test-65b7dbddd4-wdz56   1/1     Running   0          104s
      
      

      
      
      
      
      
      
      
      

      
      
      
      What is making the difference
      

      
      
      
      
      

      • cluster_compute_config resource is the difference or resource use to enable or disable EKS auto Mode in the module side.

      
      

      • At the terraform
        
        

        
        
        
        
        

        CODE Kopieren

          cluster_compute_config = {
        
            enabled    = true
        
            node_pools = ["general-purpose"]
        
          }
        
        

        
        
        
        
        
        
        
        
        
        
        • Due to cluster_compute_config option, now I don't have to mention
          eks_managed_node_group_defaults, eks_managed_node_groups, node_security_group_additional_rules or even know what are those concepts.
        
        
        
        
        

        
        

        The following code might look small but if someone who does know about EKS and node provisioning has to understand the concepts as well figure out how to write this code. But now due to EKS Auto mode no more management. WOW just so sleek.
        
        

        
        

        
        
        
        
        

        CODE Kopieren

        # code which is not needed anymore
        
        
        
        eks_managed_node_group_defaults = {
        
            ami_type       = "AL2_x86_64"
        
            instance_types = ["m5.large"]
        
            # instance_types = ["t3.small"]
        
            # vpc_security_group_ids = [aws_security_group.all_worker_mgmt.id]
        
            iam_role_additional_policies = {
        
              ebs_policy                                 = "arn:aws:iam::aws:policy/service-role/AmazonEBSCSIDriverPolicy" #IAM rights needed by CSI driver
        
              auto_scaling_policy                        = "arn:aws:iam::aws:policy/AutoScalingFullAccess"
        
              cloudwatch_container_insights_agent_policy = "arn:aws:iam::aws:policy/CloudWatchAgentServerPolicy"
        
              xray_policy                                = "arn:aws:iam::aws:policy/AWSXrayWriteOnlyAccess"
        
            }
        
          }
        
        
        
          eks_managed_node_groups = {
        
        
        
            node_group = {
        
              min_size     = 2
        
              max_size     = 5
        
              desired_size = local.node_group_desired_size
        
            }
        
          }
        
        
        
          node_security_group_additional_rules = {
        
            http_traffic_node_to_node = {
        
              description = "Allow inbound HTTP from self"
        
              from_port   = 80
        
              to_port     = 80
        
              protocol    = "tcp"
        
              self        = true
        
              type        = "ingress"
        
            }
        
          }
        
        
        
        # For triggering managed node group desired size
        
        
        
        resource "null_resource" "update_desired_size" {
        
          triggers = {
        
            desired_size = local.node_group_desired_size
        
          }
        
        
        
          provisioner "local-exec" {
        
            interpreter = ["/bin/bash", "-c"]
        
        
        
            command = <<-EOT
        
              aws eks update-nodegroup-config \
        
                --cluster-name ${module.eks.cluster_name} \
        
                --nodegroup-name ${element(split(":", module.eks.eks_managed_node_groups["node_group"].node_group_id), 1)} \
        
                --scaling-config desiredSize=${local.node_group_desired_size} \
        
                --region us-east-1 \
        
                --profile ck-test
        
            EOT
        
          }
        
        }
        
        
        
        

        
        
        
        
        
        
        
        

        
        
        
        What isn't supported
        

        
        
        
        
        
        • For existing EKS cluster where you want to enable eks auto mode is not possible at the moment using terraform for supporting this community.
        
        
        Vollständiger Original-Bericht

        Ausführliche Details, Code-Beispiele & Hersteller-Stellungnahme auf dev.to.

        ↗ Original-Artikel auf dev.to lesen