-
Notifications
You must be signed in to change notification settings - Fork 54
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
infra: allow ssh into nodes to make debugging easier #1594
Conversation
e762c84
to
9c93775
Compare
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.
Suggest making exporting worker nodes public optional, so this could make us have more flexibilty for testing env setup.
I'll add this option. |
2324691
to
22769c0
Compare
Switching between public ip and private network is more complicated than expected. Simply disabled |
6e60fad
to
5b4fa28
Compare
Refined. If it has a public ip, it can directly communicate with Internet. If it doesn't have a public ip, use nat to communicate with Internet. |
Added option in longhorn/infra#153. |
Signed-off-by: Yang Chiu <yang.chiu@suse.com>
5b4fa28
to
af84fc3
Compare
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.
Instead of removing the private network for worker nodes, have you considered bastion way to ssh from local to the internal nodes?
Suggest this way to avoid exposing instance access for security reasons.
https://repost.aws/knowledge-center/ec2-troubleshoot-bastion-host-connection
More investigation needed. Close this for now. |
Sounds good @yangchiu |
infra: allow ssh into nodes to make debugging easier
For longhorn/longhorn#6601
Signed-off-by: Yang Chiu yang.chiu@suse.com