-
Notifications
You must be signed in to change notification settings - Fork 6
/
Copy pathK8SonUbuntuOnAWS.alt
251 lines (179 loc) · 8.69 KB
/
K8SonUbuntuOnAWS.alt
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
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
### QuickStart: Setting up a Flocker + Kubernetes Cluster
#### Step 1
> This QuickStart installs Kubernetes v1.1
[Sign up for an Amazon AWS account](https://aws.amazon.com/free)
Install Kubernetes on Ubuntu using [this guide](http://kubernetes.io/v1.1/docs/getting-started-guides/aws.html)
#### Step 2
Export some optional settings.
> NOTE: Using larger instance types will cost more. Also you do not need to set any of these options, they are defaulted. Lastly, make sure you have AWS CLI installed and configured.
{% highlight bash %}
export KUBE_AWS_ZONE=us-east-1c
export NUM_MINIONS=3
export MINION_SIZE=m3.medium
export MASTER_SIZE=m3.medium
export AWS_S3_REGION=us-east-1c
{% endhighlight %}
Create the Kubernetes Cluster
> NOTE: You will need EC2 Full access and S3 Access for this process and it could take up to 10-15 minutes to complete.
{% highlight bash %}
export KUBERNETES_PROVIDER=aws; curl -sS https://get.k8s.io | bash
{% endhighlight %}
Example Output
{% highlight bash %}
Kubernetes cluster is running. The master is running at:
https://54.175.188.62
The user name and password to use is located in /Users/username/.kube/config.
... calling validate-cluster
Waiting for 2 ready nodes. 0 ready nodes, 2 registered. Retrying.
Found 2 node(s).
NAME LABELS STATUS AGE
ip-172-20-0-103.ec2.internal kubernetes.io/hostname=ip-172-20-0-103.ec2.internal Ready 1h
ip-172-20-0-104.ec2.internal kubernetes.io/hostname=ip-172-20-0-104.ec2.internal Ready 1h
ip-172-20-0-105.ec2.internal kubernetes.io/hostname=ip-172-20-0-105.ec2.internal Ready 1h
Validate output:
NAME STATUS MESSAGE ERROR
scheduler Healthy ok nil
etcd-0 Healthy {"health": "true"} nil
etcd-1 Healthy {"health": "true"} nil
controller-manager Healthy ok nil
Cluster validation succeeded
Done, listing cluster services:
Kubernetes master is running at https://54.175.188.62
Elasticsearch is running at https://54.175.188.62/api/v1/proxy/namespaces/kube-system/services/elasticsearch-logging
Heapster is running at https://54.175.188.62/api/v1/proxy/namespaces/kube-system/services/heapster
Kibana is running at https://54.175.188.62/api/v1/proxy/namespaces/kube-system/services/kibana-logging
KubeDNS is running at https://54.175.188.62/api/v1/proxy/namespaces/kube-system/services/kube-dns
KubeUI is running at https://54.175.188.62/api/v1/proxy/namespaces/kube-system/services/kube-ui
Grafana is running at https://54.175.188.62/api/v1/proxy/namespaces/kube-system/services/monitoring-grafana
InfluxDB is running at https://54.175.188.62/api/v1/proxy/namespaces/kube-system/services/monitoring-influxdb
Kubernetes binaries at /Users/username/kubernetes/cluster/
You may want to add this directory to your PATH in $HOME/.profile
Installation successful!
{% endhighlight %}
You can view your UI by going to the `KubeUI` URL above and entering your username and password from the `.kube/config` location.
{: .img70 }
Download the `kubtctl` tool to use k8s
Use `kubctl`
> The `/Users/username/kubernetes/cluster/kubectl.sh` is from output above.
{% highlight bash %}
$ kubernetes/cluster/kubectl.sh get no
NAME LABELS STATUS AGE
ip-172-20-0-103.ec2.internal kubernetes.io/hostname=ip-172-20-0-103.ec2.internal Ready 1h
ip-172-20-0-104.ec2.internal kubernetes.io/hostname=ip-172-20-0-104.ec2.internal Ready 1h
ip-172-20-0-105.ec2.internal kubernetes.io/hostname=ip-172-20-0-105.ec2.internal Ready 1h
{% endhighlight %}
> NOTE: We suggest having a seperate node for your Flocker Control Service and Kubernetes Master Services.
Create a seperate node for you Flocker Control Service
> You can use the AWS Console Launch Wizard for this.
Use the same AMI that the Kubernetes Install is using.
{: .img90 }
Launch in the correct VPC
{: .img70 }
Use the same kubernetes KeyPair created with the above tool. It shuld look something like this.
{: .img70 }
Add the security groups for kubernetes.
{: .img70}
Finally create an elastic IP for it and associate the control service.
{: .img90}
#### Step 3
Find the security group ids for the `Master` and `Worker` nodes. You can find then with `aws ec2` or in your AWS Console.
Examples
{% highlight bash %}
kubernetes-master-kubernetes --> id: sg-0b203872
kubernetes-minion-kubernetes --> id: sg-fb203882
{% endhighlight %}
Open up Flocker ports, and app ports (Redis)
{% highlight bash %}
(Flocker)
$ CONTROLLER_SEC_GROUP=sg-0b203872
$ WORKER_SEC_GROUP=sg-fb203882
$ aws ec2 authorize-security-group-ingress --group-id $CONTROLLER_SEC_GROUP --protocol tcp --port 4523-4524 --cidr 0.0.0.0/0
$ aws ec2 authorize-security-group-ingress --group-id $WORKER_SEC_GROUP --protocol tcp --port 4523-4524 --cidr 0.0.0.0/0
{% endhighlight %}
#### Step 4
Install the [Flocker CLI](https://docs.clusterhq.com/en/latest/flocker-features/flockerctl.html)and create a yaml file to install Flocker and Install Flocker
Install CLI
{% highlight bash %}
$ curl -sSL https://get.flocker.io |sh
{% endhighlight %}
Create a `flocker.yaml`
> Example Flocker YAML.
>
> You will need to replace the Public IPs, Private IPs, Amazon Key location
> and Control Node DNS name.
{% highlight bash %}
cluster_name: my-cluster
agent_nodes:
# Replace these PUBLIC and PRIVATE IPS!
- {public: 54.88.115.196, private: 172.20.0.103}
- {public: 54.208.144.177, private: 172.20.0.104}
- {public: 54.86.193.203, private: 172.20.0.105}
control_node: ec2-52-72-122-10.compute-1.amazonaws.com # YOUR Control Node DNS
users:
- ubuntu
os: ubuntu
private_key_path: /Users/username/.ssh/kube_aws_rsa #Your Pub Key for `kube_aws_rsa`
agent_config:
version: 1
control-service:
hostname: ec2-52-72-122-10.compute-1.amazonaws.com # YOUR Control Node DNS.
port: 4524
dataset:
backend: "aws"
region: "<Your Amazon Region>" # YOUR AWS Region
zone: "<Your Amazon AvailabilityZone>" # YOUR AWS AvailabilityZone
access_key_id: "<Your AWS Key>" # YOUR AWS AccessKey
secret_access_key: "<Your AWS Secre Key>" # YOUR AWS SecretAccessKey
{% endhighlight %}
> Hint: You can find the IPs easily with the AWS CLI if you want. Examples below.
{% highlight bash %}
# (Controller IP)
$ aws ec2 describe-instances --filter Name=tag:Name,Values=kubernetes-master | grep -A1 "PublicIpAddress"
"PublicIpAddress": "52.21.59.241",
"PrivateIpAddress": "10.0.0.50",
# (Controller DNS)
$ aws ec2 describe-instances --filter Name=tag:Name,Values=kubernetes-master | grep -m 2 -e "PublicDnsName"
"PublicDnsName": "ec2-52-21-59-241.compute-1.amazonaws.com",
# (Woker Node IPs)
$ aws ec2 describe-instances --filter Name=tag:Name,Values=kubernetes-minion | grep -A1 "PublicIpAddress"
"PublicIpAddress": "54.174.43.105",
"PrivateIpAddress": "172.20.0.98",
"PublicIpAddress": "54.88.98.217",
"PrivateIpAddress": "172.20.0.99",
{% endhighlight %}
**Once your `flocker.yaml` file is complete, install Flocker with these commands.**
{% highlight bash %}
$ uft-flocker-install flocker.yaml
$ uft-flocker-config flocker.yaml
$ uft-flocker-plugin-install flocker.yaml
{% endhighlight %}
> `uft-flocker-config` might take a while as it needs to download containers
#### Configure your Flocker + K8S Cluster to use Flocker
> NOTE: You can follow manual instruction for configuration flocker [HERE](http://kubernetes.io/v1.1/examples/flocker/) or use the script below to for automation.
Run the configuration script
> You will need Python Twisted, and Python YAML installed to run this script.
{% highlight bash %}
$ git clone https://github.com/wallnerryan/kube-aws-flocker
$ .//kube-aws-flocker/config_k8s_flocker.py flocker.yaml
{% endhighlight %}
You should see output like the following if succesful.
{% highlight bash %}
.
.
Uploaded api certs
Enabled flocker ENVs for 54.86.193.203
Enabled flocker ENVs for 54.208.144.177
Enabled flocker ENVs for 54.88.115.196
Uploaded Flocker ENV file.
Configured Flocker ENV file.
Restarted Kubelet for 54.86.193.203
Restarted Kubelet for 54.208.144.177
Restarted Kubelet for 54.88.115.196
Restarted Kubelet
Completed
{% endhighlight %}
Make sure you certs are correct so you can use `flockerctl` against your cluster.
{% highlight bash %}
$ cp ubuntu.crt user.crt
$ cp ubuntu.key user.key
{% endhighlight %}