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?
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
Adding steps for code quality scanning, dependency vulnerability analysis and a license scanner certainly makes it look like you actually achieved something in the next performance review, I will give you that.
Totally unrelated, if you need to suffix a k8s deployment with "-deployment" you are a hack, a fraud, an overengineer and someone who should NOT work as software or devops engineer.
Famously so. If you want to remain unmisunderstood, make sure to use sarcasm. Draw a clear line into the shifting sand while cocking a single eyebrow. It's widely appreciated, it's an artform, and the comments are a blast. :)
