You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 25, 2024. It is now read-only.
Copy file name to clipboardExpand all lines: 01-path-basics/101-start-here/readme.adoc
+51-22
Original file line number
Diff line number
Diff line change
@@ -19,31 +19,31 @@ If you are unsure, we recommend the "Launch template with an existing VPC" optio
19
19
Click on the "Deploy to AWS" button and follow the CloudFormation prompts to begin.
20
20
21
21
[NOTE]
22
-
AWS Cloud9 is currently available in 5 regions.
23
-
Please choose the region closest to you.
22
+
AWS Cloud9 is currently available in 5 regions, and EKS is currently available in 2 regions (us-east-1 and us-west-2).
23
+
Please choose the region closest to you. If you choose a region for Cloud9 that does not support EKS, you will need to change the `AWS_DEFAULT_REGION` environment variable later.
24
24
25
25
|===
26
26
27
27
|Region | Launch template with a new VPC | Launch template with an existing VPC
The Cloud9 IDE needs to use the assigned IAM Instance profile. Open the "AWS Cloud9" menu, go to "Preferences", go to "AWS Settings", and disable "AWS managed temporary credentials" as depicted in the diagram here:
61
+
62
+
image:cloud9-disable-temp-credentials.png[]
63
+
58
64
=== Build Script
59
65
60
66
Once your Cloud9 is ready, download the build script and install in your IDE. This will prepare your IDE for running tutorials in this workshop. The build script installs the following:
61
67
62
68
- jq
63
69
- kubectl _(the Kubernetes CLI, which we'll cover in great detail later in the workshop)_
70
+
- heptio/authenticator _(for authentication to the EKS cluster)_
71
+
- updates/configures the AWS CLI and stores necessary environment variables in bash_profile
64
72
- kops _(Kubernetes Operations, which we'll also cover in detail later)_
65
-
- configures the AWS CLI and stores necessary environment variables in bash_profile
66
73
- creates an SSH key
67
74
- clone the workshop repository into Cloud9
68
75
69
76
To install the script, run this command in the "bash" terminal tab of the Cloud9 IDE:
image:cloud9-run-script.png[Running the script in Cloud9 Terminal]
76
83
77
-
[NOTE]
78
-
All shell commands _(starting with "$")_ throughout the rest of the workshop should be run in this tab. You may want to resize it upwards to make it larger.
84
+
If you deployed your Cloud9 IDE in any region not supported by EKS, you will need to manually set the `AWS_DEFAULT_REGION` environment variable to a region supported by EKS:
79
85
80
-
At this point you can restart the Cloud9 IDE terminal session to ensure that the kublectl completion is enabled. Once a new terminal window is opened, type `kubectl get nodes`. You do not have to run the command. It is normal for this command to fail with an error message if you run it. You have not yet created the Kubernetes cluster. We are merely testing to make sure the `kubectl` tool is installed on the command line correctly and can autocomplete.
One last step is required so that the Cloud9 IDE uses the assigned IAM Instance profile. Open the "AWS Cloud9" menu, go to "Preferences", go to "AWS Settings", and disable "AWS managed temporary credentials" as depicted in the diagram here:
83
-
84
-
image:cloud9-disable-temp-credentials.png[]
89
+
At this point you can restart the Cloud9 IDE terminal session to ensure that the kubectl completion is enabled. Once a new terminal window is opened, type `kubectl get nodes`. You do not have to run the command. It is normal for this command to fail with an error message if you run it. You have not yet created the Kubernetes cluster. We are merely testing to make sure the `kubectl` tool is installed on the command line correctly and can autocomplete.
85
90
91
+
[NOTE]
92
+
All shell commands _(starting with "$")_ throughout the rest of the workshop should be run in this tab. You may want to resize it upwards to make it larger.
86
93
87
94
You are now ready to continue on with the workshop!
88
95
@@ -100,14 +107,36 @@ You are now ready to continue on with the workshop!
100
107
|link:../../operations-path.adoc[Go to Operations Index]
101
108
|=====
102
109
103
-
The next step is link:../102-your-first-cluster[to create a Kubernetes cluster using kops].
110
+
The next step is link:../102-your-first-cluster[to create a Kubernetes cluster].
104
111
105
112
106
113
== Workshop Cleanup
107
114
108
115
Once you have finished with the workshop, please don't forget to spin down your cluster or you will incur additional charges.
109
116
(We will also remind you at the end!)
110
117
118
+
Ensure that you have deleted all services, etc from the `default` namespace before proceeding.
119
+
120
+
=== Using EKS
121
+
122
+
==== Delete EKS worker nodeds
123
+
124
+
Go to CloudFormation console, right click template with name 'k8s-workshop-worker-nodes' and select 'Delete Stack'
125
+
126
+
==== Delete EKS cluster
127
+
128
+
In your Cloud9 IDE, check if there are any running EKS clusters
129
+
130
+
$ aws eks list-clusters
131
+
132
+
Delete EKS cluster
133
+
134
+
$ aws eks delete-cluster --name k8s-workshop
135
+
136
+
Wait until all resources are deleted by kops
137
+
138
+
=== Using kops
139
+
111
140
==== Delete Kubernetes cluster resources
112
141
113
142
In your Cloud9 IDE, check if there are any running kubernetes cluster
@@ -120,7 +149,7 @@ Delete kubernetes cluster
120
149
121
150
Wait until all resources are deleted by kops
122
151
123
-
==== Delete Cloud9 Envionment
152
+
=== Delete Cloud9 Envionment
124
153
125
154
Go to CloudFormation console, right click template with name 'k8s-workshop' and select 'Delete Stack'
0 commit comments