Operations | Monitoring | ITSM | DevOps | Cloud

In today’s ever-changing world of DevOps, it is essential to follow best practices. That goes for security, access control, resource limits, etc. One of the most important things in the world of DevOps is continuous integration and continuous delivery, or CI/CD. Continuous integration is a crucial part of an efficient deployment. We are all guilty of repeating manual steps over and over again – especially when it comes to node configuration.

Mirco Hering is principal director of APAC DevOps and Agile with Accenture. He supports major public and private sector companies in Australia and overseas in their search for efficient IT delivery. Mirco blogs about IT delivery at NotAFactoryAnymore.com and is author of “DevOps For The Modern Enterprise: Winning Practices to Transform Legacy IT Organizations.”

The traditional method of planning server, network, and storage capacity is to look at the usage peaks and then add a safety margin. Most cloud hosting is planned this way. The idea that you only pay for what you use is not based on actual usage, rather on the capacities you initially specify. Most cloud migrations involve a ‘lift and shift’ approach of moving an application to a different host with minimal maintenance.

Terms such as DevOps, Agile and LEAN are now used in a single bundle. If a project is created according to the LEAN methodology, all processes become more efficient with DevOps and Agile, making it possible to remain flexible and respond quickly to changes. In this article, we will share seven best practices you need to follow when adopting a DevOps model.

Helm is a popular open-source tool used to manage and configure your Kubernetes cluster. Basically, it is a package manager (think Homebrew or NPM) built for Kubernetes. It helps automate processes like installing, configuring, upgrading, and removing items. This post will give you a brief introduction to Helm and how it might help you manage your Kubernetes cluster.