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 +4 -4
- data/README.md +15 -9
- data/lib/eks_cli/iam/client.rb +1 -1
- data/lib/eks_cli/k8s/configmap_builder.rb +1 -1
- data/lib/eks_cli/version.rb +1 -1
- metadata +1 -1
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA1:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: db3e72f358690e91b457a14a2965971c5c7f8096
|
4
|
+
data.tar.gz: a1188295b0461d98b40a370985c8801b206fdf79
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
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.
|
20
|
-
$ eks create us-west-2 --cluster-name
|
21
|
-
$ eks create-nodegroup --cluster-name My-EKS-Cluster --group-name nodes --ssh-key-name my-ssh-key --
|
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
|
-
|
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
|
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
|
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
|
data/lib/eks_cli/iam/client.rb
CHANGED
data/lib/eks_cli/version.rb
CHANGED