![Implementing Continuous Delivery[1] at enterprise scale is a major challenge. As every company has to innovate their software delivery methods, we need to allow individual teams to learn and improve their own delivery pipeline. This is especially true in the Cloud Native world, where many best practices are still emerging. However, giving teams flexibility to experiment needs to be balanced with security and compliance requirements. In this post, I will explore how we successfully employed the GitOps architecture pattern to find a good balance between flexibility and security at a large enterprise customer of Container Solutions. This article focuses on enterprise companies with tens or hundreds of development teams. I will also assume Kubernetes as the application runtime platform. While the principles outlined here can be applied in other platforms, Kubernetes really shines in making Continuous Delivery easier to implement, and this simplification helps with making the article more focused. Finally, this will be a technical article, but not a very deep one. I will explain the solution on the level of boxes and arrows, and maybe follow up with a more detailed technical description later. Source: container-solutions #cicd #cloudnative #gitops #jenkins #london #newyork #manhattan #kubernetes #devops #sre #cloud #aws #gce #azure #iac #automation #news #services @asksendai](http://scontent-lax3-2.cdninstagram.com/vp/de0e81bab7cd0cbd3015be21669723b9/5CF64975/t51.2885-15/e35/s320x320/47582669_2240627892931040_5010989669450851102_n.jpg?_nc_ht=scontent-lax3-2.cdninstagram.com)
In Docker, How-to, OpenEBS, Solutions, Workloads
ARMing Kubernetes with OpenEBS #1
418 Views April 2, 2018 5 Comments
Running stateful containers on Le Potato Why not! It’s fun and extremely efficient! I know many people (including me) used to run ownCloud on their desktop computers. I have…