eks_cli 0.1.6 → 0.1.7

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: 22350ee29cfbc535b744189a8c4ccafc08c6f636
4
- data.tar.gz: e22b96f6721ecab906ba9220ae27e39a0d5e25c9
3
+ metadata.gz: db3e72f358690e91b457a14a2965971c5c7f8096
4
+ data.tar.gz: a1188295b0461d98b40a370985c8801b206fdf79
5
5
  SHA512:
6
- metadata.gz: 47a77f799f44e5664cec74104d6ab217ba1780cf4a3b4f46159ccd1a6820c6ceaedb35b0107fa12f9dc178e47c9b5fd0bbd5e8617391e9b966f6e9f64b62e9fa
7
- data.tar.gz: cf738bb420aed7e184451bc6ab143fc15bc323644cee5252d15b1364894c303cfdc46f9c9832b092369b6f96044b698335df10642c76e261390c4e788a62babb
6
+ metadata.gz: adadae25deffad969e6e357f76372a41e1646f337308483fb10fbb7dcf700084341cf4d77f391dceebeed43f433eed9669e3495764adc16a3e50f5a8a2810e8a
7
+ data.tar.gz: 77e388b3a33309427255d85b9663e72144f3f8aeeab91a53b0e521acaa0a9dfde016494ccad7becbc1fb1996355f172793dacb91b05678e93b157d79f60d3379
data/README.md CHANGED
@@ -16,11 +16,9 @@ EKS cluster bootstrap with batteries included
16
16
  ## Usage
17
17
 
18
18
  ```
19
- $ gem install eks_cli -v 0.1.6
20
- $ eks create us-west-2 --cluster-name=My-EKS-Cluster
21
- $ eks create-nodegroup --cluster-name My-EKS-Cluster --group-name nodes --ssh-key-name my-ssh-key --min 1 --max 3
22
- $ eks create-nodegroup --cluster-name My-EKS-Cluster --group-name other-nodes --ssh-key-name my-ssh-key --min 3 --max 3 --instance-type m5.2xlarge
23
- $ eks create-nodegroup --all --cluster-name My-EKS-Cluster --yes
19
+ $ gem install eks_cli -v 0.1.7
20
+ $ eks create us-west-2 --cluster-name My-EKS-Cluster
21
+ $ eks create-nodegroup --cluster-name My-EKS-Cluster --group-name nodes --ssh-key-name my-ssh-key --yes
24
22
  ```
25
23
 
26
24
  You can type `eks` in your shell to get the full synopsis of available commands
@@ -33,17 +31,25 @@ You can type `eks` in your shell to get the full synopsis of available commands
33
31
 
34
32
  ## Extra Stuff
35
33
 
34
+ ### Creating more than a single nodegroup
35
+
36
+ Nodegroups are created separately from the cluster.
37
+
38
+ You can use `eks create-nodegroup` multiple times to create several nodegroups with different instance types and number of workers.
39
+ Nodes in different nodegroups may communicate freely thanks to a shared Security Group.
40
+
36
41
  ### Authorize an IAM user to access the cluster
37
42
 
38
43
  `$ eks add-iam-user arn:aws:iam::XXXXXXXX:user/XXXXXXXX --cluster-name=My-EKS-Cluster --yes`
39
44
 
40
- Edits `aws-auth` configmap and updates it on EKS
45
+ Edits `aws-auth` configmap and updates it on EKS to allow an IAM user access the cluster via `kubectl`
41
46
 
42
47
  ### Setting IAM policies to be attached to EKS nodes
43
48
 
44
49
  `$ eks set-iam-policies --cluster-name=My-EKS-Cluster --policies=AmazonS3FullAccess AmazonDynamoDBFullAccess`
45
50
 
46
- Makes sure all nodegroup instances are attached with the above policies once created
51
+ Sets IAM policies to be attached to nodegroups once created.
52
+ This settings does not work retro-actively - only affects future `eks create-nodegroup` commands.
47
53
 
48
54
  ### Routing Route53 hostnames to Kubernetes service
49
55
 
@@ -66,7 +72,7 @@ Installs the nvidia device plugin required to have your GPUs exposed
66
72
 
67
73
  `$ eks set-docker-registry-credentials <dockerhub-user> <dockerhub-password> <dockerhub-email> --cluster-name My-EKS-Cluster`
68
74
 
69
- Adds your dockerhub credentials as a secret and attaches it to the default serviceaccount imagePullSecrets
75
+ Adds your dockerhub credentials as a secret and attaches it to the default ServiceAccount's imagePullSecrets
70
76
 
71
77
  ### Creating Default Storage Class
72
78
 
@@ -84,7 +90,7 @@ Creates kube-dns autoscaler with sane defaults
84
90
 
85
91
  `$ eks set-inter-vpc-networking VPC_ID SG_ID`
86
92
 
87
- Assuming you have some shared resources on another VPC (an RDS instance for example), this command open communication between your new EKS cluster and your old VPC:
93
+ Assuming you have some shared resources on another VPC (an RDS instance for example), this command opens communication between your new EKS cluster and your old VPC:
88
94
 
89
95
  1. Creating and accepting a VPC peering connection from your EKS cluster VPC to the old VPC
90
96
  2. Setting route tables on both directions to allow communication
@@ -69,7 +69,7 @@ module EksCli
69
69
  end
70
70
 
71
71
  def node_policies
72
- config["iam_policies"]
72
+ config["iam_policies"] || []
73
73
  end
74
74
 
75
75
  def arn(p)
@@ -12,7 +12,7 @@ module EksCli
12
12
  cm.metadata.namespace = "kube-system"
13
13
  cm.data = {}
14
14
  cm.data.mapRoles = map_roles(node_arns)
15
- cm.data.mapUsers = map_users(users)
15
+ cm.data.mapUsers = map_users(users) if users && !users.empty?
16
16
  cm
17
17
  end
18
18
 
@@ -1,3 +1,3 @@
1
1
  module EksCli
2
- VERSION = "0.1.6"
2
+ VERSION = "0.1.7"
3
3
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: eks_cli
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.1.6
4
+ version: 0.1.7
5
5
  platform: ruby
6
6
  authors:
7
7
  - Erez Rabih