If your build pipeline is anything more than a deploy.sh file containing

  docker build -t your-docker-registry/xxx:latest .

  docker push your-docker-registry/xxx:latest

  kubectl rollout restart deployment xxx-deployment

There are so many issues with what you have here… where to start…

You aren’t running tests, unless you put them in the dockerfile which is a bad idea…

You aren’t running security scans. how do you deploy manifest changes? Using Latest as a tag has so many issues.

This is a trivial and niave pipeline I would expect from a junior or intern.

Build pipelines are becoming more complicated because software is more complex. You can still promote ownership of the full pipeline while giving developers control.

Don’t shy away from it, understand it, embrace it. It’s just going to continue getting more complex

Mom, didn't we talk about not posting to hacker news when you're like this?

Thankfully k8s is not overengineered or you’d have pie on your face.

If your build pipeline is anything more than a monkey scratching bits into a spinning disk using a needle, you are a fraud.

No plan survives contact with the enemy.

Sure, "docker push" is all fine and well until "after two weeks, [your] coworker still does not have access to the server endpoint that he and [you] would need". And then what? Do you quit your job for fear that someone calls you a hack?

Wait, my docker registry has no authorization? Uh oh

If your build pipeline is anything more than a deploy.sh file containing

go build binary

scp binary root@server:/deploymentlocation

you are a hack, a fraud, an overengineer and someone who should NOT work as software or devops engineer.

Yes, all development is just backend web development and CRUD apps.

If you're doing anything else, are you really an engineer?

bwahaha.

Uses kubernetes, blames others for over engineering. Are we living in a parody? Oh wait…

yeah sure....