Skip to content
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.

Sign up for GitHub

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

Create nodeToAwsUser.txt #56

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Create nodeToAwsUser.txt #56

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions Chapter06/nodeToAwsUser.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
During application of Kubernetes in AWS EKS, I see it would save the reader few hours of working if in the section 6.4.2 (Using an AWS Elastic Block Store), we add some note to remind the reader that the EBS volume must in the same AZ with Pod, otherwise Kubernetes can not create volumeattachment.

This is also the feature of AWS EBS, I myself forget this, and it tooks me few hours to fingure it out.

My temporary solution when using EBS for pod is:
- Label the node that is in the same AZ with EBS.
- Add nodeSelector to the Pod so that it is assigned to node that is in the same AZ with EBS volume.