April 28, 2022
How GitOps Enables A Continuous Application Lifecycle
In our recent white paper, we take a deeper look at the true definition of continuous delivery, and how GitOps enables it. In addition to showing you what an actual GitOps pipeline looks like, we also take you through all the important tools that you’ll need to learn about like Helm, Flux, Flagger, and of course Weavework GitOps.
April 19, 2022
Profile Layering for Helm Encourages Self Service for Kubernetes
In this blog, we explain how to build a self-service Kubernetes platform with Helm, GitOps, and Cluster API. Profile layer models are the foundation for deploying whole clusters on demand and building platforms for developers with all the components they need. As a result, developer iterations make it into production faster.
April 14, 2022
The GitOps Guide to Building & Managing Internal Platforms
In our most recent white paper “The GitOps guide to building and managing internal platforms” we uncover the delivery of a self-service developer experience. In order to improve overall organizational productivity and development velocity, there is a growing emphasis on the developer experience team and how they collaborate with the platform team.
September 30, 2021
DX at the Department of Defense: Platform One and GitOps
The Department of Defense’s software development efforts span across government staff and private sector contractors and runs at 100k big. That’s a massive operation to run; one that has to be run in an extremely secure way. And yet, the DoD strives to run it in a modern way too. This post explores how the DoD wants to provide their teams the best developer experience possible without hindering any security measure and have decided to do it through the DoD DevSecOps Initiative and Platform One
September 23, 2021
Give developers the autonomy to choose their own stack
Organizations rely on their development teams to stay competitive in a fast-moving world of cloud-native applications. Yet, these developers are slowed down by operational hassles, red tape, and silos that exist within the organization. The result is that new features are deployed late, and even when deployed, potentially not stable. Highly mature DevOps organizations encountered a solution: empower developers with the autonomy to choose their own tech stack.