A couple of days ago, I was pleasantly surprised to suddenly see a tweet come in from Viktor Farcic. Viktor now works at upbound.io who developed Crossplane, and he also runs his own popular YouTube channel and co-hosts DevOps Paradox podcast. He’s well respected in the cloud native community. When I saw the tweet and noticed that Viktor had recorded a review of Civo on YouTube, I was just hoping he was kind to us...and I am pleased to say he was!

As organizations look to adopt Kubernetes, they are being confronted with a growing number of Kubernetes distributions, services, and products to choose from. Navigating the Kubernetes landscape can be incredibly challenging, especially because there is no “one size fits all” solution. To help streamline the process, we compare Red Hat OpenShift and D2iQ Kubernetes Platform (DKP) across the top production-grade capabilities to consider while evaluating an enterprise Kubernetes solution.

With DevOps teams moving at ever greater speed, it’s vital for security teams to be deeply involved at all stages of the software development and delivery lifecycle. Breaking down silos between development, operations, and security teams ensures that security considerations are not overlooked, that vulnerabilities are caught early, and that security checkpoints do not slow down the delivery process.

In this episode of the Break Things on Purpose podcast, we speak with Taylor Dolezal, Senior Developer Advocate at HashiCorp.

It’s no secret that the software development community is starting to embrace GitOps. With the complexity of engineering modern software today, it is becoming a necessity for many companies to reassess their software development and delivery practices. When Codefresh first released GitOps 2.0 late last year, we had already planned to make it a core pillar of our platform.

It’s never been more critical to protect your data infrastructure against malicious actors, with organizations dealing with an ever-expanding number of increasingly sophisticated attacks. Monitoring solutions represent part of your infrastructure’s attack surface area – they enjoy highly privileged access to the systems they help manage, and store sensitive information about the workloads running on them.

Do blameless retrospectives (or postmortems) help your team? We will explain what they are, if they really work, and how to do them right. A blameless postmortem (or retrospective) is a post-incident document that helps teams figure out why an incident happened, and brainstorm how to improve the process to prevent similar incidents from happening again. In most engineering organizations, everyone agrees that in complex systems, failure is inevitable.