oleg_log

Deploy binary like in old times.

For the last 3 years, I have had a mix of services: k8s and just a binary. As you can easily guess, the latter works flawlessly, scp'- like tool, `systemctl restart and done.

TBH, I cannot recall a problem with ssh, like I really cannot. You have a key locally, a key on the bastion machine, and 99% of the stuff is done now.

With k8s, everything is amazing globally: unified deployment, hire and fire humans without a problem. The next one will read the same yaml madness. Indeed nice.

But how much time was wasted in my team on k8s ecosystem is unreal. You can try to argue that the team had a little experience in k8s but not (not full-time k8s ops, that's true).

I think this is mostly a Go feature now; having the ability to deploy binary is a lost art in the 21st century 😢 Ah, YMMV.

PS: yeah, we had a problem with ssh deploys: removing old binaries.

www.tgoop.com/oleg_log/5962

1.2K viewsOleg, Apr 26, 2024 at 07:07

Deploy binary like in old times.

For the last 3 years, I have had a mix of services: k8s and just a binary. As you can easily guess, the latter works flawlessly, scp'- like tool, `systemctl restart and done.

TBH, I cannot recall a problem with ssh, like I really cannot. You have a key locally, a key on the bastion machine, and 99% of the stuff is done now.

With k8s, everything is amazing globally: unified deployment, hire and fire humans without a problem. The next one will read the same yaml madness. Indeed nice.

But how much time was wasted in my team on k8s ecosystem is unreal. You can try to argue that the team had a little experience in k8s but not (not full-time k8s ops, that's true).

I think this is mostly a Go feature now; having the ability to deploy binary is a lost art in the 21st century 😢 Ah, YMMV.

PS: yeah, we had a problem with ssh deploys: removing old binaries.

BY oleg_log