While Kubernetes has been traditionally used with Linux workloads, the desire to run Windows applications is an important need for many organizations that have critical applications running on Windows Server. Docker has already offered support for native Windows containers, so the next missing piece would be Windows node support in Kubernetes clusters. Google Cloud has recognized this gap and is now offering Windows support for Kubernetes clusters.

One of the most critical metrics when it comes to the software delivery process is deployment frequency, which measures how often releases are happening in production. While in theory all organizations should strive to deploy as often as possible, in practice the benefits for frequent deployments are often overlooked or buried under endless technical debates.

Building upon the success of Helm 2, Helm 3 has recently been released and the server-side component, Tiller, is finally gone! Helm works out-of-the-box with Coderesh, so releasing your Helm 3 applications is as easy as pie. In this blog post, you will learn about viewing Helm releases, and monitoring Helm environments. Still using Helm 2? Not to worry! With a click of a button, in Codefresh, you can manage both Helm 2 and Helm 3 clusters simultaneously!

Engineering and “the business” don’t always speak the same language. That’s why in this blog post and webinar, we want to show you how to bridge the gap using the language “the business” understands: cold hard cash. When talking to the business value, here are four areas that DevOps provide value for your organization with associated calculators so you can get an exact value to share with your organization.

Kubernetes offers scalability and reliability for your container-based applications. Combine this with GKE, and you now eliminate the need to install or operate clusters on your own. A huge plus to using GKE is that you now will be running Kubernetes in a GCP environment, therefore you can utilize all the handy integrations Google has to offer. Codefresh simplifies the process even more, by automating the process of getting your code built, tested, and deployed.

In our previous announcement for the removal of the Codefresh Docker registry, we presented a timeline of the migration phases along with the actions expected from our customers. One of the milestones in the migration process is the introduction of our new Image API along with several enhancements on the pipeline build step. We believe that these features deserve a dedicated explanation of why they are useful on their own (regardless of the registry removal).