We are hoping to fix this problem internally with documentation, but we have seen this process fail when the user's shell was currently in a directory that they could not write to. I am not sure whether we should prefix the name of the CA certificate with ~/.kube or just ~/ or /tmp/whatever... long story short, if they are not in a writable directory when they copy/paste the steps, it will fail in ways that are not very clear.
We are hoping to fix this problem internally with documentation, but we have seen this process fail when the user's shell was currently in a directory that they could not write to. I am not sure whether we should prefix the name of the CA certificate with ~/.kube or just ~/ or /tmp/whatever... long story short, if they are not in a writable directory when they copy/paste the steps, it will fail in ways that are not very clear.