With enterprises and ISVs adopting containers and Kubernetes (k8s) to increase the agility and scalability of their applications, they would want more applications to be deployed on k8s. Applications can be a mix of stateful and stateless. Until recently, only stateless applications were supported by k8s. However, with the advent of persistent storage on k8s, stateful applications will be supported. In the pet Vs cattle analogy of service, you would want to treat the storage as cattle.

One of the most popular cloud disaster recovery models in the industry today is the “pilot light” model where critical applications and data are in already place so that it can be quickly retrieved if needed. A simple question one must ask before adopting this model is what thought has been given to whether the AWS/GCP/Azure APIs will work and if the requisite capacity will be available in the alternate region.

Introduction One of the SRE team’s goals at Moogsoft is to make sure our feature teams have an easy path from local code changes to production. Changes rolling out to production mean new features, bug fixes, optimizations, and more, which translates into value added for our customers. In short, at Moogsoft we are all about making sure our product is continually evolving, and one way the SRE group helps is by building shared Jenkins functionality our engineers understand and can use quickly.

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.