Skip to content
This repository was archived by the owner on Apr 25, 2024. It is now read-only.

Commit 2b8dc12

Browse files
author
Scott Malkie
committed
Continue formatting 101-102; Move 40x modules around to add admission-policy
1 parent c2855d7 commit 2b8dc12

31 files changed

+4
-6
lines changed

01-path-basics/101-start-here/readme.adoc

+3-2
Original file line numberDiff line numberDiff line change
@@ -9,9 +9,10 @@ This tutorial will walk you through the process of creating a Kubernetes develop
99
== Create AWS Cloud9 Environment
1010
=== AWS Cloud9 Console
1111

12-
It is possible to create and configure the Cloud9 development environment via CloudFormation.
13-
This CloudFormation template will create the Cloud9 IDE, IAM Role required for kops, and the S3 bucket for the kops state store.
12+
We can create and configure the Cloud9 development environment via CloudFormation.
13+
This CloudFormation template will create the Cloud9 IDE, the IAM Role required for kops, and the S3 bucket for the kops state store.
1414

15+
[NOTE]
1516
AWS Cloud9 is only available in 5 regions currently. Please choose the region closest to you geographically.
1617

1718
|===

01-path-basics/102-your-first-cluster/readme.adoc

+1-4
Original file line numberDiff line numberDiff line change
@@ -55,7 +55,7 @@ Once the `kops create cluster` command is issued, it provisions the EC2 instance
5555

5656
Note: If your 'create cluster' fails with an error like:
5757
```
58-
error reading s3://example-kops-state-store-workshop/workshop-prep.cluster.k8s.local/config: Unable to list AWS regions: NoCredentialProviders: no valid providers in chain
58+
error reading s3://example-kops-state-store/example.cluster.k8s.local/config: Unable to list AWS regions: NoCredentialProviders: no valid providers in chain
5959
caused by: EnvAccessKeyNotFound: failed to find credentials in the environment."
6060
```
6161
Try setting the following environment variables before executing the 'create cluster' command:
@@ -164,9 +164,6 @@ If multiple clusters exist, then you can change the context:
164164

165165
$ kubectl config use-context <config-name>
166166

167-
168-
169-
170167
image:next-step-arrow.png[ , title="Continue!"]
171168
You are now ready to continue on with the workshop!
172169

5.29 KB
Loading

0 commit comments

Comments
 (0)