-
Notifications
You must be signed in to change notification settings - Fork 519
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
QUICKSTART: add easier setup instructions using new eksctl release #849
Conversation
@@ -12,14 +12,89 @@ Once you have a cluster, you can skip to the last step, [Launch!](#launch) | |||
## Dependencies | |||
|
|||
EKS has a command-line tool called `eksctl` that makes cluster setup easy. | |||
First, get [eksctl set up](https://github.com/weaveworks/eksctl). | |||
Versions of eksctl starting with 0.15.0-rc.2 support Bottlerocket natively. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: the prior line uses the code type face, so let's keep using that.
Versions of eksctl starting with 0.15.0-rc.2 support Bottlerocket natively. | |
Versions of `eksctl` starting with `0.15.0-rc.2` support Bottlerocket natively. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The code style is there to introduce a new name, but afterward I think it would seem like scare quotes..?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks really good!
21e9af6
to
0892c83
Compare
This push addresses (most of) @jahkeup's and @samuelkarp's comments. |
0892c83
to
3c66f91
Compare
This push fixes the other |
Testing done:
I created clusters with each of these configs and the new instructions, confirming they were able to run pods and connect via SSM. I confirmed that the sample config with SSH was able to connect to the admin container via SSH, and the other was not. The system seemed healthy.