<p>I have a minikube K8s 1 node cluster on my Windows 10 pc. I can SSH into this cluster using <code>minikube ssh</code>.</p>
<p>The problem that I am experiencing is that I can't use the arrow keys to bring back the previous command. I did some looking around and diagnostics:</p>
<ul>
<li><code>set -o | grep history</code> gave <code>history         on</code></li>
<li><code>echo $HISTFILE</code> gave <code>/home/docker/.bash_history</code>. This is indeed in the home folder of the user and the file was present after <code>exit</code>ing and executing <code>minikube ssh</code> again</li>
<li><code>echo $HISTSIZE</code> and <code>echo $HISTFILESIZE</code> both gave 500</li>
<li><code>echo $SHELL</code> gave <code>/bin/bash</code></li>
</ul>
<p>All these things tell me that command history should be enabled, but it doesn't seem to be the case.
I tried using both Powershell and cmd to run <code>minikube ssh</code>, both with and without Windows Terminal.</p>
<p>Both PowerShell and cmd themselves have a working command history, but once SSHing using minikube, the history in the bash shell doesn't work.</p>
<p>Does anyone know how to get the command history to work after executing <code>minikube shh</code>?</p>
<p><strong>Edit:</strong>
I have tried <code>minikube ssh --native-ssh=false</code>, but this didn't change anything.</p>

<p>It seems to be a problem with the SSH client you are using. You can try with the <em><code>--native-ssh=false</code></em> option:</p>
<pre><code>minikube ssh --native-ssh=false
</code></pre>
<p>You can also try with different alternatives or with something like the ssh version that comes with <a href="https://www.cygwin.com/" rel="noreferrer">Cygwin</a>.</p>
<p><a href="https://github.com/kubernetes/minikube/issues/5666" rel="noreferrer">There is already an unsolved issue related to this</a>. (Feel free to update)</p>
<p>✌️</p>
