-
Notifications
You must be signed in to change notification settings - Fork 0
/
cluster.yaml
62 lines (55 loc) · 1.29 KB
/
cluster.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
---
apiVersion: eksctl.io/v1alpha5
kind: ClusterConfig
metadata:
name: Nginx-cluster
region: us-east-1
vpc:
id: "vpc-0b1aca68fd4cd169d"
cidr: "172.31.0.0/16"
subnets:
public:
us-east-1a:
id: "subnet-065f318450ec070c2"
cidr: "172.31.0.0/20"
us-east-1c:
id: "subnet-05f8e5caca5b10498"
cidr: "172.31.16.0/20"
private:
us-east-1d:
id: "subnet-05aa5c31ed3abe2c7"
cidr: "172.31.32.0/20"
us-east-1b:
id: "subnet-0d3d859fe0d06b33c"
cidr: "172.31.64.0/28"
managedNodeGroups:
- name: managed-NG-public
instanceType: t3.medium
minSize: 1
desiredCapacity: 2
maxSize: 3
subnets:
- subnet-065f318450ec070c2
- subnet-05f8e5caca5b10498
volumeSize: 20
updateConfig:
maxUnavailable: 1
securityGroups:
attachIDs: ["sg-0184afd669d60b043"]
ssh:
allow: true
publicKeyPath: ~/.ssh/id_rsa.pub
labels: { role: worker }
tags:
nodegroup-role: worker
iam:
withAddonPolicies:
externalDNS: true
certManager: true
- name: managed-NG-private
instanceType: t3.medium
# launch nodegroup in private subnets
privateNetworking: true
subnets:
- subnet-05aa5c31ed3abe2c7
- subnet-0d3d859fe0d06b33c