In SSM add support for AWS-StartPortForwardingSessionToRemoteHost to use a jumphost to eks #38
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
boris-smidt-klarrio
force-pushed
the
master
branch
from
565f78a to
dfc3a67
Compare
boris-smidt-klarrio
force-pushed
the
master
branch
from
39ed6c6 to
078d2e2
Compare
|
Basically you are doing nearly exactly the same thing I'm doing in my PR from yesterday: I'm fine with merging either of them, both should lead to the same result. |
|
Ah yes, funny 👍 I hope one of ours gets merged soon! |
|
closing in favor of #36 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We use a jumphost to reach our kubernetes clusters using ssm.
For this we need support to have support to do an ssm actuion named AWS-StartPortForwardingSessionToRemoteHost which requires different parameters than the StartSSHSession.