The idea is better than port knocking, in the sense that you take active action to associate your host with the server, but there's a few issues. * Something t

The idea is better than port knocking, in the sense that you take active action to associate your host with the server, but there's a few issues. * Something this simple shouldn't need k8s, unless it was intended as an exercise by the developer for that reason * It combines the idea of using a non-standard port with certificate based authentication, which you can already do with SSH-- it's functionally the same with more steps Hypothetically, this approach can be more powerful as a centralized service running elsewhere, (i.e. cloud, your remote DC) and used for a whole bunch of jump boxes and end-users. End-users could run a "check-in" script wrapping around SSH that notified the service that a user was imminent, and then could check the server to see if 1) The bearer token is accepted for the destination server 2) That the destination server checked in, saw the new incoming request, and has already opened the port -- And then proceeds to run the SSH command if all is well, or fails with appropriate error.