scrambler

James, we respectfully disagree. I think it's helpful if you (or anyone reading this) compare two projects side by side. This is the project you have submitted: https://github.com/jameskeane/scrambler It is a prototype of IPSec CNI plugin using Bash. We are happy you are promoting your project online and as we've discussed during the interview, you could use it as you wish as it's your work. This is the project that we have created at Gravitational: https://github.com/gravitational/wormhole It is using Go, Wireguard and is designed for production use under Apache 2 license. I understand that similarities in the problem statement may have led you to believe that we could re-use the project idea, I'm assuring that you that we have not. There are many OSS CNI plugins in the market solving the similar problem in a similar fashion (e.g. flanne

Check out Scrambler: https://github.com/jameskeane/scrambler It's basically this, but with ~100 lines of bash. As simple as it gets.

Do you feel bad about using your 'hiring process' as a means of free labour? i.e. Reading kubeadm config, reusing system certs, and automating the configuration of a VPN overlay system: https://github.com/jameskeane/scrambler -- FYI to readers, the above project was completed as part of a 'take-home assignment' that I was explicitly told was not a project being worked on. The feedback I received indicated that this approach was not considered previously, and may indicate (also your commit dates) that this entire project may have been fabricated after my submission. Here's the feedback from Gravitational around Oct 2018 (before this project was 'started'): > * I do think re-using the kubernetes certs for IPSec is a compelling solution for the IPSec secrets > * I like the re-use of the kubernetes keys/certs for ipsec as it avoids use of the