The purpose of best practices

When the DevOps team first started out on the journey of automation, they were trying to script deployments to application servers. As the server pools and customer base grew, so did the need for more reliable deployment methods. These requirements changed rapidly as the company moved toward a cloud-native approach. The desire to adopt container-based and serverless applications with cloud infrastructure became the main drive behind the move for increased automation efforts. As the DevOps team built out a potential deployment solution for containers and Kubernetes, the directives once again shifted to include a broad range of platforms and architectures. Adding to the consistent scope of support shifting was a deadline that remained relatively consistent. This meant that the DevOps team had little time to document and plan, but rather had to implement a solution that was an inexpensive, high-quality product, and did so in a short period of time. And as...