0.9.0

What's Changed

• Support finding jump pod by labels by @partcyborg in #25

Full Changelog: 0.8.1...0.9.0

0.8.1

What's Changed

• Add amd64 to nodeSelector in default Pod template by @yokawasa in #24

Full Changelog: 0.8.0...0.8.1

0.8.0

What's Changed

• docs: fix typo by @BenjaminHerbert in #21
• Support providing namespace and context by @partcyborg in #23

New Contributors

• @BenjaminHerbert made their first contribution in #21

Full Changelog: 0.7.3...0.8.0

0.7.3

What's Changed

• Fix connection closed by remote host issue (closed by unknown port 65535) by @yokawasa in #20
  • Add RSA workaround options (-o HostkeyAlgorithms=+ssh-rsa -o PubkeyAcceptedAlgorithms=+ssh-rsa) to commands in ProxyCommand only if the local OpenSSH version >= 8.5

Full Changelog: 0.7.2...0.7.3

0.7.2

What's Changed

• Fix Bad configuration option: pubkeyacceptedalgorithms issue by @yokawasa in #19
  • Add RSA workaround options (-o HostkeyAlgorithms=+ssh-rsa -o PubkeyAcceptedAlgorithms=+ssh-rsa) which was first added in PR #17 only if the local OpenSSH version >= 8.5
  • Add verbose option for debugging
• Add verbose option (-v|--verbose)
  Full Changelog: 0.7.1...0.7.2

0.7.1

What's Changed

• Fix [email protected]: Permission denied issue cased by newer ssh client (OpenSSH 8.8+) by @yokawasa in #17
  • Add -o HostkeyAlgorithms=+ssh-rsa -o PubkeyAcceptedAlgorithms=+ssh-rsa for RSA deprecation workaround
  • NOTE: RSA was deprecated in OpenSSH 8.8

Full Changelog: 0.7.0...0.7.1

0.7.0

What's Changed

• Support specifying a custom sshjump pod template by @partcyborg in #14

New Contributors

• @partcyborg made their first contribution in #14

Full Changelog: 0.6.0...0.7.0

0.6.0

Support SSH local port forwarding to access a remote server. This allows to forward the traffic form local machine to SSH jump then SSH jump will forward the traffic to the remote server - #12

About SSH local port forwarding with kubectl ssh-jump

Suppose you have private & public SSH key on your side and you want to access a remote server (IP: 10.100.10.8) using 3389/TCP port which is not accessible directly but accessible via SSH jump, execute the plugin with options like this, at first:

• identity:~/.ssh/id_rsa_k8s
• pubkey:~/.ssh/id_rsa_k8s.pub)

The command below allows to forward the traffic form local machine (localhost:13200) to SSH jump then SSH jump will forward the traffic to the remote server (10.100.10.8:3389).

$ kubectl ssh-jump sshjump \
  -i ~/.ssh/id_rsa_k8s -p ~/.ssh/id_rsa_k8s.pub \
  -a "-L 13200:10.100.10.8:3389"

• sshjump is the hostname for SSH jump Pod
• The value for --arg or -a should be in this format: "-L local_port:remote_address:remote_port"

Now, you're ready to access to the remote server at port 13200 at local machine.

0.5.0

• Fix to address pod sshjump pod scheduling on hybrid clusters (PR#9, thanks to @swgriffith )

0.4.0

Support PEM (Privacy Enhanced Mail) scenario where you create key-pair but you only have .pem / private key (downloaded from AWS, for example) and you don't have the public key on your side.

example

Suppose you've already downloaded a pem file and you want to ssh to your EKS worker node (EC2) named ip-10-173-62-96.ap-northeast-1.compute.internal using the pem, execute the plugin with options like this:

• usernaem: ec2-user
• identity: ~/.ssh/mykey.pem

$ kubectl ssh-jump -u ec2-user -i ~/.ssh/mykey.pem ip-10-173-62-96.ap-northeast-1.compute.internal