0

Some context:

I have little experience with ci/CD and manage a fast paced growing application since it saw the light of the day for the first time. It is composed by several microservices at different environments. Devs are constantly pushing new code to DEV , but they frequently forget about sending new values from their local .env ove to the openshift cloud, regardless of this being a brand new environment or existing ones.

The outcome? Services that fail because they lack to have their secrets updated.

I understand the underlying issue is lack of communication between both us DevOps staff and devs themselves. But I've been trying to figure out some sort of process that would make sure we are not missing anything. Maybe something like a "before takeoff checklist" (yes, like the ones pilots do in a real flight preparation): if the chack fails then the aircraft is not ready to takeoff.

So the question is for everyone out there that practices DevOps. How do you guys deal with this?

Does anyone automates this within Openshift/kubernetes, for example? From your perspective and experience, would you suggest any tools for that, or simply enforce communication?

2
  • New to DevOps but a check before deployment on your platform would be ideal, maybe a human step in the deployment process May 14 at 12:48
  • @GeorgeUdosen I agree. Having pretty much everything automated has its shortcomings as well. I mean, they push code and it's automatically builder and deployed. Automation can be a blessing and a curse sometimes. To waive that would open space for a human step. But do we really want to relinquish an auto-deploy feat?
    – the_piper
    May 14 at 18:33

0

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.