EKS v1.12

[MilanDasek]

Hello,

how can I deploy EKS v1.12 using eksctl?

Here is my config:

apiVersion: eksctl.io/v1alpha4
kind: ClusterConfig

metadata:
  name: eks-production
  region: eu-west-1

tags:
  environment: production

node-volume-size: 100
node-ami: auto

nodeGroups:
  - name: ng1-eks-production
    instanceType: t3.medium
    minSize: 0
    maxSize: 0
    labels:
      lifecycle: Ondemand
      environment: production
      autoscaling: enabled
    iam:
      withAddonPolicies:
        autoScaler: true
        ExternalDNS: true
        ImageBuilder: true
        ebs: true
        fsx: true
        efs: true
    availabilityZones: ["eu-west-1a", "eu-west-1b", "eu-west-1c"]
    privateNetworking: true
    AllowSSH: true

vpc:
  id: "%ID%"
  cidr: "10.2.32.0/20"   
  subnets:
    private:
      eu-west-1a: {id: %ID%}
      eu-west-1b: {id: %ID%}
      eu-west-1c: {id: %ID%}
    public:
      eu-west-1a: {id: %ID%}
      eu-west-1b: {id: %ID%}
      eu-west-1c: {id: %ID%}

This deploys 1.11

Also node-volume-size is still 20GB, not 100.

Please advise.

Thank you

[romilpunetha]

apiVersion: eksctl.io/v1alpha4
kind: ClusterConfig
metadata:
  name: eks-test
  region: ap-south-1
  version: "1.12"
  tags:
    version: test
    billing: core
    sub-billing : kubernetes
    environment: test
vpc:
  id: "vpc-xxxxxxxx" 
  cidr: "192.168.x.x/16"
  subnets:
    private:
      ap-south-1a:
          id: "subnet-xxxxxxxx"
          cidr: "192.168.x.x/24"
      ap-south-1b:
          id: "subnet-xxxxxxxx"
          cidr: "192.168.x.x/24"
    public:
      ap-south-1a:
          id: "subnet-xxxxxxx"
          cidr: "192.168.x.x/24"
      ap-south-1b:
          id: "subnet-xxxxxxxx"
          cidr: "192.168.x.x/24"
iam: 
  serviceRoleARN: "arn:aws:iam::xxxxxxxxxxx:role/EKS"
nodeGroups:
  - name: eks-spotinst
    labels: 
      applicationType: org
      machineSize: mixed
    instanceType: t2.xlarge
    desiredCapacity: 1
    ami: ami-09c3eb35bb3be46a4
    minSize: 1
    maxSize: 1
    volumeSize: 50
    volumeType: gp2
    privateNetworking: true
    maxPodsPerNode: 50
    allowSSH: true
    sshPublicKey: 'eks-bastion'
    availabilityZones: ["ap-south-1a", "ap-south-1b"]
    iam:
      withAddonPolicies:
        imageBuilder: true
        autoScaler: true

[errordeveloper]

Yeah, it's just not the default yet.

[MilanDasek]

@romil-punetha

Can I ask, you have

nodeGroups:
  - name: eks-spotinst
    labels: 
      applicationType: org,
      machineSize: mixed,

so you then change launch configuration to enable spots manually in aws? Or is possible to have it somehow in eksctl config?

thanks

[whereisaaron]

Hi. You have the wrong name for the volume size setting and AMI. Those are the command line option names. Check the read me examples.

[romilpunetha]

@MilanDasek I actually use spotinst. So they need one instance, fully configured from where they import configurations, and then you can define launch specifications there which is similar to the nodegroup configurations. They set up spot instances for me, and fall back to on-demand when spot instances are not available. I migrated my test cluster setup to spotinst, and will move the stage and prod clusters as well.

[errordeveloper]

Making spot instance is on the roadmap post v1alpha5, i.e. hopefully before end of April.

On Fri, 5 Apr 2019, 3:03 pm Romil Punetha, notifications@github.com wrote:

@MilanDasek https://github.com/MilanDasek I actually use spotinst. So they need one instance, fully configured from where they import configurations, and then you can define launch specifications there which is similar to the nodegroup configurations. They set up spot instances for me, and fall back to on-demand when spot instances are not available. I migrated my test cluster setup to spotinst, and will move the stage and prod clusters as well.

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/weaveworks/eksctl/issues/709#issuecomment-480287021, or mute the thread https://github.com/notifications/unsubscribe-auth/AAPWS_qRDDAUSkq27l_ViMvnTFTh1pRCks5vd1eogaJpZM4ce2C_ .